Optiak Docs
Administration

Members and Access

Manage who can join your organization and what each person or group can access.

Membership controls who can sign in to your organization. Role assignments determine which organization settings, projects, applications, and request data each member can see or change.

Required role

Organization AdminWorkspace Admin

Applies to

Administrative actions
Organization Admins manage members, groups, and organization roles. Organization Admins and Workspace Admins can grant project roles.

Sign in to Optiak

Sign in through the Auth0 screen using email and password, Google, Microsoft, or your company's SSO when it is configured. Your organization also has an SSO sign-in link built from its slug (/enterprise/<organization-slug>); share it with teammates so they can sign in directly with your company's identity provider, and find it in Settings → Organization. After authentication, Choose your organization lists the organizations your account can access. Select one to open Optiak, including when you have a single or previously used organization.

Authentication verifies your identity; membership determines which organizations you can access. Accounts without an organization continue to plan selection. If you were invited to an existing organization, reopen your invitation or contact its administrator. Invitation links keep their existing flow and open the invited organization after acceptance.

Why use it

Use membership to let someone sign in, then use roles to decide what they can see or change. For example, a project role can give a teammate access to that project's applications without granting access to every project. If several teammates need the same access, assign a role to a group and manage them together.

How it works

Access has four parts:

  • Membership determines whether someone can sign in. Membership alone does not grant project access.
  • Role determines what actions they can take.
  • Scope determines where the role applies. Organization Admin and Workspace Admin roles apply across the organization. Project Admin, App Admin, and App Viewer roles apply to every application in one project.
  • Combined access includes roles assigned directly and roles inherited through groups. These permissions add together, so removing one grant may leave access from another role or group.

For example, Alice has App Admin in the Analytics project, so they can configure every application there but get no access to Billing from that grant. If a group also gives Alice App Viewer in Analytics, revoking the direct App Admin grant removes the ability to configure applications, but Alice keeps the access granted by the group.

You can assign a role directly to a person or to a group. A user must already be a member of the organization before you can grant them a role. You can grant a role while their invitation is pending, but it does not provide access until they accept and their membership becomes active. For the resource hierarchy, see Organization and Projects.

Organization

A member must belong here before receiving a role.

A person joins or is invited

01

Membership

Membership lets someone sign in; it does not grant project access.

Active member

Can sign in to the organization.

Pending invitation

No access until the invitation is accepted.

Access starts after acceptance

02

Role assignment

Grant a role directly to a member or to a group.

Direct assignment

The member receives the role themselves.

Group assignment

Members inherit roles granted to their group.

The selected role sets the scope

03

Where access applies

Organization and project roles cover different resources.

Organization role

Applies across the organization, its projects, and applications.

Project role

Applies to every application in the selected project.

Members

Use Members to see who belongs to your organization, when they joined, and whether an invitation is still pending. Organization Admins and Workspace Admins can view the list; only Organization Admins can add or remove members.

To add someone, enter their name and email address. You can use an address from another domain or add someone who already has an Optiak account. Depending on your sign-in setup, they may get access right away or need to accept an invitation first. A person with a pending invitation cannot access the organization.

After opening an invitation, the person chooses how to sign in unless the invitation limits them to a method you configured. At least one sign-in method must be available to both the organization and application. If the person already has an Optiak account, their sign-in identity must already be linked to it; matching email addresses alone do not link accounts. For help with organization sign-in methods, select Get help in the console to contact Optiak Support.

After adding someone, Invitation requested means the provider accepted the request. It does not confirm that the email reached their inbox; check the status in Members. Removing a pending member stops their invitation from granting access. Removing an active member revokes their organization membership, so they can no longer sign in to or access its resources. If provider-side cleanup fails, their local access still stays revoked and support may need to finish the cleanup. This differs from revoking a role; see Set it up.

Invitations

The Members list shows membership state separately from invitation status, and displays an invitation's expiry when available. Use Refresh status before retrying if a request is still sending or its outcome is unknown.

Member added

The membership may activate now or wait for an invitation.

No invitation required

The member becomes active immediately.

Active membership

The person can sign in; project access still depends on their roles.

Invitation required

The member stays pending until they accept.

Sending invitation

A request is in progress. Refresh status before retrying.

Invitation requested

Awaiting acceptance

The provider accepted the request; this does not confirm email delivery.

Invitee accepts

Invitation accepted

Membership is active; roles determine project and application access.

If the invitation needs attention

Check the status before retrying an uncertain request.

Expired, invalid, or failed

An Organization Admin can resend. If sending failed, correct the reported cause first.

Invitation status unknown or unavailable

Refresh status. Resend can reconcile an uncertain request; contact support if the result stays unclear.

An Organization Admin can resend an invitation to someone who is still pending. If the invitation is limited to a sign-in method, resending keeps that choice. Make the method available again before resending if needed; otherwise, the invitee chooses how to sign in.

If you aren't sure whether an invitation was sent, refresh the Members list before trying again. Resend may recover the existing invitation without sending another email; the system does not retry automatically. A successful recovery shows Invitation ready. Only one resend can run for a member at a time, and any provider error appears beside that member.

Sometimes a request fails even though the member was added. The form checks Members before letting you try again, to help prevent duplicates. If it cannot check, select Check members. If you find the person in the list, review their invitation status and use Resend if needed instead of adding them again.

At least one sign-in method must be eligible for both the organization and the application. If configuration or provider lookup fails when you submit the invitation, correct the configuration or explicitly retry when the provider is available. Switching organizations closes and clears the invitation form.

Groups

A group is a named set of organization members. Use one when several people need the same project access, so you can grant a role once and manage membership in one place. Only Organization Admins can create, edit, or delete groups, and add or remove their members.

Groups can contain only people who are already members of the organization. Invite a new person from Members first, then add them to a group. Removing someone from a group removes access they inherited through that group, but not access from their direct role assignments or other groups.

Roles

Roles can be assigned only at the organization or project scope. The project roles apply to every application in that project; you cannot assign a role to just one application.

Permission summary

The table summarizes the access each role provides. Organization Admins have all permissions listed. Organization roles apply across the organization; project roles apply within their project. Membership lets a person sign in, but does not grant role permissions; the Sign in row reflects active membership. A Member has no role permissions. A dash means the role does not grant that action.

Access by role
Action Org Admin Workspace Admin Project Admin App Admin App Viewer Member
View Company Setup, provider keys, members, and audit logs✓✓————
Manage Company Setup and provider keys✓—————
Create or delete projects✓✓————
Grant organization roles✓—————
Grant project roles✓✓————
Manage groups✓—————
Create or delete applications✓✓✓———
Configure applications✓✓✓✓——
View individual requests✓✓✓✓——
View supported application configuration and metrics✓✓✓✓✓—
Sign in✓✓✓✓✓✓

Set it up

In the console, open Settings, then Members, Groups, or Access, depending on what you need to manage.

To give someone access, open Access and select Grant access. Organization Admins can choose a person or group and grant a role across the organization or in one or more projects. Workspace Admins can choose a person or group and grant a role in one or more projects, but not across the organization. The available roles depend on the selected scope. You can grant access to a person with a pending invitation; a Pending invite badge marks them, and the role takes effect once they accept.

After you grant access, the list shows who has each role, where it applies, who granted it, and when. A Pending invite badge next to a name shows the grant is waiting on invitation acceptance. Search or filter the list, or export it to review the grants.

To revoke a role, remove that assignment from Access. Revoking one assignment does not remove membership or other access the person receives from another role or group. To remove a person's ability to sign in, remove them from Members instead.

Limits and behavior

  • An organization must always have at least one effective Organization Admin. You cannot revoke your own Organization Admin assignment or remove the last effective Organization Admin, including when that access comes through a group.
  • App Viewers cannot access Tools with the App Viewer role alone because it does not include access to the organization's tool setups.
  • A role assignment grants access only to its scope. Project roles apply to all applications in that project, not to individual applications.
  • Organization and Projects: how projects group applications and how applications are managed.
  • Authentication: how to create and manage Application API keys and organization connections.
  • Audit Logs: review recorded changes to members, groups, and role assignments.
Copyright © 2026