Skip to content

Settings

Everything configurable lives behind Settings in the sidebar. The page is organized into three scopes, and you see only what your role lets you act on.

Per-user, available to everyone:

  • Profile — your name and details.
  • Password and sessions — change your password, review active sessions.
  • Access tokens — your API tokens.
  • Notifications — which events notify you, in-app and by email.

The operational settings for the active workspace — visible to workspace admins (and, for some tabs, testers):

  • General — the workspace name and description.
  • Members & teams — who’s in the workspace, and their roles.
  • Auth fixtures — how OttoTester signs in to test (set up authentication).
  • Integrations — provider connections (GitHub for deployment-driven trigger rules and PR Check Runs, Slack for run notifications). Connect or disconnect each provider here; pick which repo or default channel each application uses on the application’s own Integrations tab.

A workspace reviewer doesn’t see the Workspace section at all — read-only roles get account settings only, by design.

The governance settings for the active organization — owners and admins edit, billing sees billing, members get a read-only view:

  • General — the organization name.
  • Members and Teams — org membership and groups.
  • Workspaces — the list of workspaces; create new ones here.
  • Billing — payment and plan (owner and the billing role).
  • Audit log — a record of significant actions.
  • Recovery — restore a recently deleted workspace or org.

If a tab or control you expect isn’t there, it’s a role limit, not a bug — OttoTester hides what you can’t change. Check your role against Roles and permissions, and ask an admin if you need more access.