Teams & Sharing
Teams, member roles, private vs. team documents, share links, invitations, and how access works in Doczoid.
Everything in Doczoid lives inside a Team. Teams own your docs, presentations, and PortalSnips, and they control who can see and edit what.
Teams
A team is the shared home for your content. All members of a team can work with the team's documents and presentations according to their role. Even a solo user has a team — a team of one.
Roles
Team membership comes with a role that determines what a member can do:
| Role | Typical capability |
|---|---|
| Owner | Full control of the team, its content, and its members |
| Admin | Manage content and members |
| Member | Create and edit content |
| Viewer | Read-only access |
Private vs. team documents
Each document can be private or shared with the team:
- Private — visible only to the person who created it.
- Team — visible to everyone on the team.
This lets you draft in private and publish to the team when you're ready.
Inviting people
Team owners can invite collaborators from the share menu:
- By email — send an invitation directly; the recipient gets a link to accept (or to sign up and join if they're new). Invitations expire after 7 days.
- By link — copy an invite link or its QR code to share however you like.
Inviting members requires a Team subscription. Accepted and declined invitations trigger a notification so you know the outcome.
Sharing a document
Documents support sharing via links, each available with a copyable QR code:
- Public link — a read-only link that anyone can open. It's off by default; enable it per document, and disable it anytime to revoke access.
- Team (internal) link — a link only your team's members can access. Always available for quick internal sharing.
Enable or disable sharing per document, so you stay in control of what's exposed.
Versioning and collaboration
Sharing a document means people work in it together. That's backed by Doczoid's full collaboration toolset — live editing, presence, comments, and version history that records who changed what. PortalSnips can even be locked to a specific document version for stable reuse.
Related
- Core Concepts — how teams, docs, and snips relate.
- Collaboration — what happens once people are working together.
- PortalSnips — team-owned reusable content.