Team Management
Workspaces, members, roles, and permissions
Team Management
Membership
Access to Parslinks is organized around the workspace. Members are invited by email; an invitation can be accepted by an existing account or start a new one. Pending invitations can be resent or revoked by workspace admins.
Roles
Roles apply at two levels:
| Level | Roles | Controls |
|---|---|---|
| Workspace | Owner, Admin, Member | Workspace settings, billing, invitations |
| Project | Admin, Member | Project resources and actions |
Project-level roles refine what a member can do inside a specific project:
- Project admin: full control — deleting services (including volume wipe), managing environments, minting console sessions
- Project member: day-to-day operations — deploys, variable changes, viewing logs and metrics
Some sensitive actions require explicit elevation regardless of role:
- Deleting a service with volume wipe needs project admin
- Doing so when a production environment exists additionally requires an explicit acknowledgement in the confirmation step
Projects visibility
Projects can restrict membership: on shared projects every workspace member gets baseline access, while restricted projects only admit explicit project members. This also affects elevated tools — for example, the interactive console requires project-admin on restricted projects.
Notifications
Members receive in-app notifications for events on their projects — deployment successes and failures, invitations, invoices. Email delivery applies to the events marked transactional (invitations, invoice ready) plus your personal security emails (password changes, verification).
Leaving & removal
- A member can leave a workspace themselves from account settings.
- Admins can remove any member; the member's API sessions are revoked.
- Ownership transfer follows the standard flow: promote another admin to owner before leaving if you're the last owner.