Roles and permissions
Teams
Roles and permissions inside Teams
Permissions significantly change what a user can create, approve, see, or manage.
If your organization uses Teams, not every user works with the same scope. The extension distinguishes between owner, admin, editor, and viewer.
Understanding this avoids common confusion such as not being able to publish shared content or not seeing content that does exist in another department.
Role summary
| Role | What it can do | What to remember |
|---|---|---|
| Owner | Manages the entire organization, configuration, visibility, and critical flows. | This is the profile with the broadest operational reach. |
| Admin | Manages shared content, approvals, and broad team settings. | Usually can see more departments than a regular user. |
| Editor | Creates and edits working content. | In workspaces with approvals, what they publish may stay pending until review. |
| Viewer | Consults shared content. | Usually does not create or modify resources in the common space. |
Scope across departments
When the company enables strict isolation, regular users only see content from their own department or from the general segment. Owner and Admin usually keep wider visibility for supervision and workspace governance.
If something does not appear, do not assume it was deleted: it may be outside your reach because of role, department, or approval status.