Team and roles

What a workspace is

A workspace is the unit that owns your licences, projects, and tokens. Every customer gets one automatically the first time they buy or activate something on Packagento; you only need to think about roles when you have more than one developer working out of the same workspace.

Manage your team from Org settings. The page lists current members and pending invites, and the workspace switcher at the top lets you flip between any workspace where you are an owner or admin.

Workspace-level roles

Five roles can be assigned at the workspace level. They are ranked, and when you invite someone, you can only grant a role at or below your own rank.

owner

The original creator of the workspace. Can invite at any role, including granting owner.

admin

Manages team and projects. Can invite up to admin; cannot grant owner. Most "team lead" cases sit here.

developer

Default role for invited engineers. Reads project tokens, installs packages, and rotates tokens. Does not edit workspace membership or billing.

billing

For finance or ops folks. Can request refunds and cancel subscriptions on workspace licences; cannot read project tokens.

viewer

Read-only on members, projects, and licences. No token access. Useful for auditors or transient access reviews.

Project-level guest roles

Workspace owners, admins, and developers already have project access via their workspace role. Project-level roles exist for guest cases where you want to grant access to one specific project without making someone a workspace member.

developer (project guest)

Reads the project's tokens (to paste into auth.json), sees the licences activated on the project, and can rotate tokens.

viewer (project guest)

Sees project metadata and the licence list but cannot read or rotate tokens.

Removing someone from a project ends their guest access to that project only; they keep any other access they have through their workspace role or other project guest invites.

Invite a new member

From Org settings click "Invite a member". Provide an email address and pick a role; the invitee receives an email with an acceptance link valid for 14 days.

Only workspace owners and admins can send invites. The role picker offers developer, admin, billing, and viewer; granting owner is reserved for the existing owner.

Acceptance flow:

• If the invitee already has a Packagento account, the link signs them in (if needed) and adds them to the workspace with the role you set.
• If they don't, the link routes them through registration first; once they create the account, they are added to the workspace automatically.

Acceptance links are single-use. Once accepted, revoked, or expired, the link no longer works. You can revoke a pending invite from the members list at any time.

Removing a member

When a member is removed, any project tokens they personally minted on the workspace's projects are deactivated automatically. Tokens minted by other teammates keep working, so you do not need to rotate every token on every project after a single departure. Rotate only the tokens you specifically want to retire.

There is always at least one owner per workspace. Today, removing the owner and transferring ownership is a support-assisted operation; contact support if you need to hand a workspace off to a new owner.

Multiple workspaces

A single Packagento customer can be a member of more than one workspace: their own, plus any that other customers invited them into. The Org settings switcher flips between the workspaces where you are an owner or admin. Licences, projects, and tokens are scoped to the workspace they belong to and never leak across.

Troubleshooting

• Invite link expired: the workspace owner or admin can re-issue from the members list. Acceptance links are single-use and time-bound by design.
• Member can't see project tokens: the billing and viewer roles do not include token access. Grant developer (or use a project-level developer guest invite) instead.
• Need to grant owner: only the existing owner can grant owner. An admin can invite at most another admin.
• Wrong workspace context: check the workspace switcher at the top of Org settings. It is common to be invited into another customer's workspace and forget which one is active.