Roles & Permissions
Understand what each Revibu role can access and do inside your workspace.
Revibu workspaces are collaborative by design.
To keep things safe and organized, every member has a role with specific permissions.
You can invite teammates from Workspace Settings → Members, then assign a role at any time.
Roles overview
Revibu includes five roles:
- Owner (full control)
- Admin (almost full control)
- Developer (product + automation control)
- Support / Agent (reviews + internal tickets)
- Viewer (Read-only) (view only)
Owner
Owner is the highest permission level.
Owners can do everything in the workspace, including the most sensitive actions.
Owners can:
- Manage the organization / workspace
- rename workspace
- change settings
- delete workspace
- Manage members and roles
- invite / remove users
- promote / demote roles
- Manage the subscription & billing
- upgrade / downgrade plan
- update payment method
- cancel subscription
(Owners are the only ones who can access billing.)
- Manage tool integrations
- connect / disconnect Jira / Linear / Notion (OAuth)
- configure delivery settings (Owners only.)
- Manage store integrations
- connect App Store / Google Play
- enable backfill
- manage reply publishing
- Manage automations
- create / edit / delete / activate rules
- Access all reviews, tickets, alerts, dashboards, exports
Typical Owner: Head of Product, CTO, or whoever pays for Revibu.
Admin
Admins can manage almost everything except billing and tool OAuth.
Admins can:
- Manage workspace settings except deletion
- Manage members & roles (except changing Owners)
- Manage store integrations
- Manage automations
- Manage internal tickets & dashboards
- Publish / validate replies
- Configure alerts
Admins cannot:
- Access or change subscription / billing
- Connect / disconnect Jira / Linear / Notion
- Change delivery OAuth settings
- Delete the workspace
Typical Admin: Product Lead, Engineering Manager.
Developer
Developers focus on review triage and automation.
Developers can:
- Manage store integrations
- connect / reconfigure App Store / Google Play
- Manage automations
- create / edit / activate rules
- Access reviews & internal tickets
- Comment on internal tickets
Developers cannot:
- Manage subscription / billing
- Manage members & roles
- Connect Jira / Linear / Notion OAuth
- Delete workspace
Typical Developer: Mobile lead, QA, growth engineer.
Support / Agent
Support/Agents are built for daily review handling.
They have read access to most areas, but can act on reviews and internal tickets.
Support/Agents can:
- Read dashboards, apps, automations, and settings
- Go to Reviews
- view & filter reviews
- draft replies
- publish replies (if allowed by store integration settings)
- Use the internal Issue Board
- comment on tickets
- change internal status / priority / labels (if enabled in your workspace policy)
- assign tickets to teammates
Support/Agents cannot:
- Change workspace settings
- Manage members & roles
- Manage store connections
- Manage automations
- Connect Jira / Linear / Notion
- Access billing
Typical Support/Agent: Customer support rep, community manager.
Viewer (Read-only)
Viewers can only observe.
Viewers can:
- Read reviews, tickets, dashboards, automations, settings
Viewers cannot:
- Reply to reviews
- Create/edit automations
- Comment or edit tickets
- Connect integrations
- Manage workspace or billing
Typical Viewer: Stakeholders who need visibility without action.
Quick permission matrix
| Capability | Owner | Admin | Developer | Support / Agent | Viewer |
|---|---|---|---|---|---|
| Billing / subscription | ✅ | ❌ | ❌ | ❌ | ❌ |
| Connect Jira / Linear / Notion (OAuth) | ✅ | ❌ | ❌ | ❌ | ❌ |
| Configure Issue Sync delivery | ✅ | ❌ | ❌ | ❌ | ❌ |
| Connect stores (App Store / Play) | ✅ | ✅ | ✅ | ❌ | ❌ |
| Create / edit automations | ✅ | ✅ | ✅ | ❌ | ❌ |
| Reply to reviews | ✅ | ✅ | ✅ | ✅ | ❌ |
| Manage internal tickets | ✅ | ✅ | ✅ | ✅ | ❌ |
| Invite / remove members | ✅ | ✅ | ❌ | ❌ | ❌ |
| Delete workspace | ✅ | ❌ | ❌ | ❌ | ❌ |
Best practices
- Keep 1-2 Owners max.
- Make your Product/Engineering leads Admins.
- Give mobile/QA owners Developer for automations.
- Give frontline teams Support/Agent for replying and ticket follow-up.
- Use Viewer for stakeholders.
If you want, I can also write a short “which role should I pick?” section per team type (B2B SaaS, games, fintech, etc.).