Team Access

Team access determines who can view, manage, and operate Olyx resources. Use account-level membership for organization-wide access and project-level membership for scoped project work.

Access Levels

Olyx separates access by account and project.

ScopeUse it for
Account-wide accessPeople who need visibility across the workspace
Project accessPeople who only need one project
Internal Olyx dashboardOlyx staff-only operational view, not customer access

Roles

Roles determine what a user can change. The dashboard exposes management actions only to authorized members.

Typical role behavior:

RoleCommon capability
OwnerManage account, projects, team, keys, and sensitive settings
AdminManage operational settings and project resources
MemberView and operate within assigned permissions

Invite Members

Use the account or project team page to send invites.

Recommended invite pattern:

  1. Invite the user at the narrowest useful scope.
  2. Assign the least privileged role needed.
  3. Confirm the invite is accepted.
  4. Review access after the user no longer needs it.

Edit And Remove Access

Authorized members can:

  • edit a member role
  • remove a member
  • update a pending invite role
  • revoke a pending invite

Membership changes are audit-relevant. Review audit history after major access changes.

Project Scoping

Logged-in project pages should only show resources for the selected project. For example, keys, models, traces, and replays from another project should not be visible through project-scoped views.

When testing access:

  1. Create two projects.
  2. Create a key in each project.
  3. Sign in as a scoped member.
  4. Confirm the member sees only the expected project resources.

Session Safety

Dashboard sessions are browser sessions. Do not share URLs as a substitute for access control. If a user is not authenticated and authorized, the server should redirect or reject the request before rendering the resource.

Next Steps

Was this page helpful?