Skip to main content

Team

Organization billing, project members, roles, and project keys.
1 min read

An organization owns billing and org members. A project under it owns taste, keys, and collaborators. Org members do not automatically see every project.

Members#

/{org}/{project}/settings/members

Invite by email to this project. Built-in project roles: owner, admin, member. Custom roles pick from the same ACL. Accept also adds the person as an organization member if they are not already in the org.

Roles#

/{org}/{project}/settings/roles

Do not edit owner, admin, or member.

PermissionWhat it allows
taste.readList, get, and open a suggestion
taste.writePropose, accept, reject, merge (default member has this)
taste.deleteDelete proposed forks
policy.writeThe same actions when the item is a policy
Note

taste.publish is on owner and admin in the role list. Accept today is gated by write, not publish.

Project keys#

/{org}/{project}/keys

CLI grants and CI keys for this project. Prefix st_. Revoke from here. Login mints a key for one project.

Billing#

/projects/billing and /projects/invoices

Sip is 1/month(1 / month (10 / year). Stack is 9/month(9 / month (90 / year). Billed on the organization, covers every project in it. Invited members do not pay and do not see this page unless they can manage org billing.

Coming soon#

Packs and CI checks are in the sidebar as Coming soon.