Permissions and roles
An organization role controls administration; a resource permission controls access to a particular piece of work. Being an admin does not automatically grant Manage on every resource.
Organization roles
| Role | What it controls |
|---|---|
| Admin | Organization administration, including invitations, member management, and settings, subject to plan availability |
| Member | Creating and using work within the organization, subject to plan availability and resource access |
An admin still needs the appropriate resource permission to manage that resource. To invite an outsider from a resource’s sharing panel, the sender must be both an organization admin and a manager of the resource. A member can request an admin’s approval instead.
Resource permissions
| Level | What it allows |
|---|---|
| Viewer | Read or open a resource without editing its definition |
| Editor | Edit the resource |
| Manage | Edit the resource and manage its sharing, with actions such as renaming or deleting where supported |
General access and invitations sent by email do not grant Manage. After an invitee accepts, someone who manages the resource can update their permission when needed.
Access can come from a direct share, a team, or an enclosing folder. Removing one share may leave access through another route. Change inherited access at its source. For app-specific capabilities, the Builder label, and general access settings, see Sharing apps with your team.
Team roles
| Role within a team | What it controls |
|---|---|
| Admin | Managing that team’s membership alongside organization admins |
| Member | Belonging to the team and receiving access shared with it |
A team role is separate from the person’s organization role. Review team membership and resource sharing together when someone changes responsibilities. See Groups and teams to organize people and share with a team.
Still stuck? Email support@play.fast