Two layers: workspace roles and space access
Emitii separates who someone is in the company from what they can do in a particular space.
Workspace roles
| Role | What it means |
|---|---|
| Owner | Full control. Owner-only powers include billing, domains, deleting or transferring the organisation, and assigning other owners. |
| Admin | Runs the Admin console: people, invitations, guests, groups, departments, permissions, spaces, meeting rooms and AI settings, within the powers the owner allows. |
| Member | A regular employee. Works in the spaces they have access to. |
| Guest | An outside person, such as a client, invited to specific spaces only. See guest access. |
Space access levels
Inside a space, each person has one of four levels:
- No access
- View only: read, but not change.
- Can contribute: create and edit work, comment, upload.
- Can manage: everything, including settings, members and approvals.
The built-in roles that carry these levels are Viewer, Contributor and Manager.
Access per area
A space is not all-or-nothing. Levels can be set per area: Board, Tasks, Schedule, Timesheets, Posts, Activity and Docs & Files. Some examples:
- A designer can contribute on the Board and Docs & Files but only view the Timesheet.
- A finance lead can manage Timesheets, approving weeks, without managing the Board.
- A stakeholder can view everything and change nothing.
Access adds up
Grants in Emitii combine and never narrow. If a person gets View only from their department and Can contribute from a group, they have Can contribute. Nothing someone is given in one place is taken away by a grant somewhere else. This keeps the model predictable: to see why someone can do something, look at what they have been given, not at a chain of exceptions.
Guests follow their own rules: they can view or contribute in the sections a space opens to them, but they never manage a space.
Granting access to many people at once
Admins manage access in Admin > Permissions ("Workspace permissions"). Grants can go to:
- Everyone in the workspace.
- A department, such as Design or Finance.
- A group, such as "Client A team" or "Leads".
- A person.
Grants cover spaces, channels and admin powers. Groups and departments are created and managed in the Admin console, and people are placed in them from Admin > People.
Custom roles and admin powers
Beyond Viewer, Contributor and Manager, admins can create custom roles for a specific mix of permissions. The owner controls which admin powers admins hold, so a company can let an admin handle invitations without letting them change access policies. Guests have their own settings: workspace defaults in Admin Console > Guests > Guest permissions, and a Guest access tab in each space that sets what guests see section by section.
What people see
Every member has a Your access page showing their level in each space, what they can start, and their role, department and groups. Admin console sections an admin lacks permission for are hidden rather than shown and refused.
Anything someone cannot open simply is not shown to them. Spaces they are not in do not appear in lists or search.
The audit log
Admin actions are recorded in Admin > Audit Log and can be filtered. Entries include actions such as "Invited user", "Set access policy", "Imported CSV" and "Changed member role", so there is a record of who changed what.
Security underneath
Emitii is invite-only, and each organisation's data is kept separate from every other organisation's, and Enterprise workspaces can have everything on their own dedicated setup. Everything is encrypted: chat messages, comments, docs, notes and files. Sessions use HttpOnly cookies, rotating refresh tokens and a 30-day absolute limit. People sign in with Google or an email and password.
Who uses it
Consulting firms keep each client's space visible only to the engagement team. Software companies give the whole company view access to product spaces while engineers contribute. Growing small businesses start with everyone as members and add departments as teams form. The business operations use case covers a wider setup.
Learn more
The admin and access docs walk through roles, groups and the permissions screen. To see it for your team, request access.
Frequently asked questions
- What roles does Emitii have?
- Workspace roles are Owner, Admin, Member and Guest. Inside a space, people have No access, View only, Can contribute or Can manage, which can be set per area.
- What does access adds up mean?
- Grants combine and never narrow. If someone gets View only from one grant and Can contribute from another, they have Can contribute.
- Can I give different access to different parts of a space?
- Yes. Levels can be set separately for Board, Tasks, Schedule, Timesheets, Posts, Activity and Docs & Files.
- Is there an audit log?
- Yes. Admin actions such as invites, role changes and access policy changes are recorded in Admin > Audit Log.
Related
- Guest accessInvite clients and partners as guests, choose what each space shows them, and share items one by one. Internal work stays internal until you share it.
- Project managementSee how Emitii runs each client, project or team in its own space, with a board, tasks, schedule, docs, chat and timesheet turned on as needed.
- Business operationsRun internal routines, policies, company updates and team admin in Emitii with Internal spaces, recurring to-dos, Posts and Docs & Files.
- Consulting firmsConsulting firms use Emitii to give each engagement one space for workplan, deliverables, client meetings and billable hours, with clients invited as guests.
- Admin & accessInvite people to Emitii, import them from CSV, add guests, organise groups and departments, set space access levels and review the audit log.