Workspace and team
Who can work in your company, with which role, and how to give someone access to just one project or chatbot.
Everything in ORYVOX belongs to a company (organization): chatbots, websites, integrations, knowledge, agents and billing. One person can be in several companies and switch between them in the top left menu. See Organizations.
Invite people
Go to Team → Add member, enter an email address and pick a role. The person gets an invitation by email. The Activity list shows who joined, left or changed role.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including naming admins and transferring ownership. |
| Admin | Everything but ownership. |
| Developer | Projects, keys, chatbots and request logs with content. |
| Analyst | Usage and logs, without content. |
| Billing manager | Plans and invoices. |
| Viewer | Dashboards only. |
Only the owner names admins. Nobody can give a role more permissions than they have themselves.
Custom roles, teams and guests
- Custom roles replace a built-in role's permissions with exactly the ones you choose.
- Teams group people inside your company, each with a lead. Access can be granted to a whole team at once.
- Guests see nothing until you grant them something, and their access can end on a date you set.
Access to one thing
You can allow or deny a person or a team access to a single project, chatbot, website, workflow or Polaris project, at three levels: view, use or manage (manage includes use, use includes view). Rules can expire.
- Deny wins. One deny for the person or any of their teams is enough.
- Inheritance. A chatbot inherits the rules of its project.
- Restricted. Once something has an allow rule, only the people it names, plus owners and admins, get in.
Sensitive actions
Changing members, roles, security, billing or API keys asks you to confirm your password again if you haven't in the last 15 minutes. Everything is written to the audit log.