Team Member Roles Explained
Overview of Roles
AppGram uses a role-based access control (RBAC) system to manage what team members can do within your organization. Each role has a specific set of permissions that determine what actions a team member can perform.
Available Roles
Owner
The highest level of access. Owners have complete control over the organization.
Permissions:
- All Admin permissions
- Transfer organization ownership
- Delete the organization
- Manage billing and subscriptions
- Cannot be removed by other members
Note: There must always be at least one Owner in an organization.
Admin
Full administrative access without organization-level destructive capabilities.
Permissions:
- All Editor permissions
- Invite and remove team members
- Change other members' roles (except Owner)
- Create and delete projects
- Manage organization settings
- Configure integrations
- Access API keys
- View audit logs
Editor
Can create and modify content within their assigned scope.
Permissions:
- All Viewer permissions
- Create and edit feedback items
- Manage roadmap items (create, update status, prioritize)
- Create and publish changelog entries
- Respond to support tickets
- Create and edit forms and surveys
- Manage help center articles
- Update status page incidents
Viewer
Read-only access to view content and analytics.
Permissions:
- View feedback and wishlist items
- View roadmap
- View changelog entries
- View support tickets (cannot respond)
- View analytics and reports
- View form submissions
- View survey responses
Role Comparison Table
| Permission | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View content | ✓ | ✓ | ✓ | ✓ |
| Create/edit content | ✓ | ✓ | ✓ | ✗ |
| Manage team members | ✓ | ✓ | ✗ | ✗ |
| Create/delete projects | ✓ | ✓ | ✗ | ✗ |
| Manage billing | ✓ | ✗ | ✗ | ✗ |
| Delete organization | ✓ | ✗ | ✗ | ✗ |
Changing Roles
To change a team member's role:
- Go to Organization Settings → Team
- Find the team member
- Click the Edit button or role dropdown
- Select the new role
- Save changes
Best Practices for Role Assignment
- Limit Owners: Keep the number of Owners minimal (1-2 people)
- Use Admins sparingly: Only give Admin access to team leads who need to manage team members
- Default to Editor: Most active team members should be Editors
- Use Viewer for stakeholders: Perfect for executives, clients, or stakeholders who need visibility
- Combine with scopes: Pair roles with appropriate scopes for granular control