Users
Each person in Skyelight has a role in each workspace they belong to. Owners, admins and collaborators take paid seats. Reviewers, usually clients and stakeholders, are free on every plan.
A role in each workspace
A person’s role applies to one workspace, so the same person can have different roles in different workspaces. For example, a freelancer can be a collaborator in one client’s workspace and a reviewer in another. There are four roles:
| Role | Who it’s for | Paid seat |
|---|---|---|
| Owner | The one person responsible for the workspace | Yes |
| Admin | Runs the workspace: people, settings, integrations | Yes |
| Collaborator | The team doing the work | Yes |
| Reviewer | Clients and stakeholders giving feedback | No |
How seats are counted
A seat is one person who holds the owner, admin or collaborator role in any workspace in the organization. A person who is an admin in one workspace and a collaborator in another counts as one seat.
Reviewers never take a seat, on any plan. They can pin, reply, react, change a thread’s type, add types, and resolve, defer or reopen any thread. They can’t assign threads, invite people or create projects.
Billing and the organization owner
Billing belongs to the organization, and one person owns it. Only the owner can change the plan or the payment method, or release unused seats. Before anyone adds a seat, Skyelight shows what it will cost. See Plans and billing.
Permissions are checked on the server
Skyelight checks a person’s role on its servers each time they open a workspace, reply or change a setting. The interface hides controls a person can’t use, but the server check is what applies. If someone reaches a control their role doesn’t allow, the action fails.