Teams & Sharing
Updated
Organisations
Work in Kwilio Projects belongs to an organisation. One account can belong to several organisations — being invited to a second workspace adds it to the account you already have rather than creating a new one, and the title bar gains a switcher naming the organisation you're working in.
Your role is per organisation. You can be an owner in one and a guest in another. Being removed from one organisation has no effect on another, and takes effect immediately rather than whenever the session happens to expire.
Roles and Access
Access has two layers: your organisation role, and per-project access on top of it. Being in the organisation does not mean seeing every project.
A project you don't have access to returns nothing at all — the error never confirms it exists.
Some actions sit with owners and admins rather than anyone with edit access:
- Shipping a release — marking a release shipped is a project lead's call
- Deleting a label — it removes that label from every task in every project
Inviting People
- Open the Team page
- Create an invitation
- Send the person the link however you already talk to them
Kwilio Projects does not email invitations. The link gives them a page that hands them the app and their code, and opens the app straight to the invitation if they already have it. Someone who's already signed in is offered the chance to join with their existing account.
People joining from an invitation aren't asked to verify their email — their organisation already vouches for the address.
Seats
A seat is an active member or a pending invite. Pending invitations count, because they're already promised.
Deactivating someone frees their seat, and their work stays attributed to them. Comments, assignments, and history don't get orphaned or reassigned.
See Billing & Account for seat limits per plan.
Activity
The activity feed shows only work you can see. Events in projects you're not a member of never appear in it.