Administration

Administration controls how your organization is configured and who can access each part of OKTO. Start with the access or configuration outcome you need and keep privileges as narrow as the role allows.

Start with a goal

What do you want to do?

Choose the outcome that matches the work in front of you. You can come back to the deeper reference sections when you need details.

01

Set up roles and permissions

Give staff and volunteers the access required for their responsibilities without exposing unrelated modules or sensitive information.

Manage roles →02

Invite or manage users

Add people to the staff workspace and manage their administrative access lifecycle.

Manage users →03

Use a permission override

Apply targeted exceptions when a role needs a narrow difference from its normal access model.

Review overrides →04

Review least privilege

Start with the smallest access level that lets someone do their job and expand intentionally as responsibilities change.

Review access model →

Recommended flow

A good first workflow

1. Define the person’s actual responsibilities in OKTO.
2. Choose the narrowest role that supports those responsibilities.
3. Use a targeted override instead of broad administrator access when an exception is required.
4. Review access when staff roles change or sensitive responsibilities are reassigned.

Team access

Use Roles & Permissions to give staff and volunteers the access they need without exposing unrelated modules or sensitive information.

• Roles & Permissions
• Users & Invitations
• Permission Overrides

Principle of least privilege

Start with the smallest access level that lets someone do their job. Expand access intentionally when responsibilities change rather than giving broad administrator access by default.