Skip to Content

Administration

Manage people, permissions, sign-in, updates and data.

Permissions decide who can do what in your Sunport. Some things wait for a person's decision, an approval, before they happen.

Use it when
You add people, share agents, or wonder why something was refused
You get
Two roles, teams, exact permissions, and approvals on record
Cost
None of their own
Setup time
One invitation per person
Needs
An administrator to change roles, teams and permissions

Roles

Everyone who signs in has one of two roles:

  • Administrator: manages people, agents, billing and settings. They hold every permission, except denies set on them.
  • User: uses the agents an administrator gives them, and sees only their own usage.

The Sunport owner is an administrator whose login only they change. A new owner is set in the OpenOrange app.

Agents

A user reaches an agent at one of two levels: Chat, or Chat and settings. Whoever creates an agent owns it. Settings › Access sets what every owner gets on their own agents.

Teams

A team is a department, and it holds permissions. Everyone in it who isn't an administrator holds them while they are in it. A new member holds them from their first sign-in. Someone who leaves loses them.

Permissions

A permission allows or denies an area, or one exact action:

  • View sees an area. Manage also changes it.
  • An exact permission is written ACTION:RESOURCE, such as billing.read:*.
  • A deny wins over any allow, a person's own included.
  • You can give only what you hold yourself.

So far the dashboard honors only some permissions, marked Works in the dashboard too. The rest work in oo and the API.

Roles, invitations and sign-ins need an administrator with full access. That is their own sign-in, or an unrestricted key of their own.

Sign-in

People sign in on your Sunport's own sign-in page:

  • with their email and password;
  • with a passkey added in Settings › Profile;
  • with a code sent to their email, while emailed codes are on;
  • with Sign in with OpenOrange, once an administrator turns it on.

The owner can also open the Sunport from the OpenOrange app.

Approvals

Some things wait for a person's decision before they happen:

  • Asked of you: an agent asks before acting for you, or asks you for a secret. Only you decide, signed in as yourself.
  • Clem's changes: some changes Clem makes for an administrator wait for their click, such as making someone an administrator. Clem lists them.
  • Pending requests: an operation waits for a person's decision. Nobody decides their own request.
  • An agent's skills: when someone who can't change an OpenClaw agent, other than Clem, has it save a skill, the people who can change it are asked. The first approval saves it; any decline ends it. The person who asked is told either way.

An approval is a record, not a permission. It grants nothing. An agent never sees a secret you type. The number beside Settings in the account menu counts what waits for you.

Limits

  • A team adds nothing to an administrator, and limits nothing. Only a deny changes what they can do.
  • Someone invited holds no permissions until they sign up.
  • Nobody changes their own role or sign-in.
  • The last active administrator can't be made a user or turned off.
  • A deny on seeing any one person keeps the whole Users list from you.
  • Clem's changes expire if nobody approves them within a day.
  • At most 10 of an agent's skill changes wait at once.

How-to guides

Data, privacy and updates

Your Sunport sends OpenOrange only what it needs, and what you choose to share. Administrators choose what is shared, what is kept, and when updates install.

Use it when
You must say what OpenOrange sees, keeps or changes
You get
Choices for sharing, request content, keys, updates and backups
Cost
Backups, snapshots and extra disk are charged to your prepaid balance
Setup time
Defaults apply until an administrator changes them
Needs
An administrator; holding the keys is the owner's

What your Sunport sends OpenOrange

Settings › Data sharing lists two kinds.

Always sent is what OpenOrange needs to run, bill and update your Sunport. Each item says why it is sent. The record of a model call through OpenOrange never holds its prompt or reply.

Optional sharing starts off until an administrator turns it on:

  • Diagnostic evidence: redacted logs from your server, to investigate a problem.
  • Investigator access: an investigator may read conversations, files and personal data.
  • AI triage of alerts: alert details go to an AI model that suggests a cause.

Two choices start differently:

  • Automatic key handoff starts on. With it off, moving to a new server needs your recovery file.
  • Error reports start on for public Sunports, and off for enterprise ones.

What is off isn't sent, and OpenOrange refuses it.

Request content

The text of model requests and replies is kept for the Requests pages. Settings › Privacy chooses:

  • how long it is kept: not at all, 7, 30 or 90 days, or forever;
  • a disk budget, past which the oldest text is cleared first;
  • whether administrators can open other people's.

Everyone can open their own. Every view is recorded in the audit log. Usage and billing numbers are always kept.

Keys

Your Sunport's keys open its conversations, request logs and nightly backups. Until you hold them, OpenOrange keeps a copy to restore or move your Sunport. The owner can hold them. OpenOrange then deletes its copy for good.

Maintenance access

OpenOrange can't sign in to your Sunport's server until an administrator opens access. Access lasts 1 hour, 24 hours, or until someone ends it. Every change is recorded in the audit log.

Updates

New OpenOrange releases install automatically, unless you hold them. Settings › Updates chooses:

  • windows when updates may start, in your time zone;
  • a hold until a date;
  • whether security updates install at once, outside your windows.

An update already running may finish. Update now asks for the newest release for your Sunport, outside your windows. While agents are working, it waits until they finish, unless you install at once. The dashboard and Clem restart, and each agent restarts in turn. New chat messages can't be sent until the update has finished. To plan updates, your Sunport tells OpenOrange how many agent runs are open and when it was last used. It also sends the browser time zone of the administrator who last used the dashboard. Managed by OpenOrange lists what OpenOrange sets for your Sunport.

Backups

Settings › Backups holds three kinds:

  • Nightly backups (off-server) copy the database, settings and files into OpenOrange's backup storage.
  • Daily backups copy a machine's whole disk once a day. The last seven are kept.
  • Snapshots copy a machine's whole disk, and stay until you delete them.

Each is charged to your prepaid balance at the provider's price.

Limits

  • Usage and billing numbers are kept whatever the content setting.
  • Holding the keys can't be undone.
  • Turning backups off deletes them, and can't be undone.
  • Update now skips your schedule, but not a hold.
  • The dashboard restores agent and service VMs only.
  • A bigger disk can't shrink again.

How-to guides

How-to guides

Invite a person

Before you start: you need to be an administrator, and your Sunport's mail must be set up. An administrator can make you one.

  1. Open Users and choose Invite.
  2. In Email, type their address.
  3. Under Role, choose User or Administrator.
  4. For a user, choose the Agents they can use.
  5. Under What they can do with these agents, choose Chat or Chat and settings.
  6. Optionally, choose a Team.
  7. Choose Send invite.

Check it worked: Invite sent. appears, and their row in Users shows Invited.

The sign-up link works once and expires. Their row's menu has Resend invite and Revoke invite.

Permissions and approvals explains roles and levels.

Approve an access request

Before you start: you need to be an administrator, signed in as yourself. An administrator can make you one.

  1. Open Users. Requests wait under Access requests.
  2. Check who wrote, and whether their email is confirmed.
  3. Choose Access to: and pick the agents they get.
  4. To tell them, turn on Email them that they're in.
  5. Choose Approve as user, or Decline.

Check it worked: the request leaves Access requests, and they appear in Users.

A request waits 14 days. After Decline, that account can't ask for that agent again for 14 days.

Permissions and approvals explains roles and levels.

Change a person's role

Before you start: you need to be an administrator, signed in as yourself.

  1. Open Users and open the person.
  2. Open the ⋯ menu beside Edit.
  3. Choose Make administrator, or Make user.
  4. Confirm with the same button.

Check it worked: their page shows Administrator or User.

Nobody changes their own role. The Sunport owner and the last active administrator can't be made users.

Permissions and approvals explains what each role holds.

Put people in a team

Before you start: you need to be an administrator. An administrator can make you one.

  1. Open Users and choose Teams.
  2. Choose New team, type a Name, and choose Create.
  3. Open the team and give it permissions under Team permissions.
  4. Open Users, open a person, and choose Edit.
  5. In Team, type the team's name and choose Save.

Check it worked: the team's People lists them.

A team gives an administrator nothing more. A team is removed only once nobody is in it and no invitation names it.

Permissions and approvals explains teams.

Give a permission

Before you start: in the dashboard, you need to be an administrator, signed in as yourself. With oo, See users (people.read) and Manage API permissions (access.manage) are enough. You can give only what you hold.

  1. Open Users, open the person, and open the Permissions tab. For a team, open Teams and the team.
  2. Choose Add permission.
  3. Under Allow or deny, choose Allow or Deny.
  4. Choose what it covers, or Choose permissions to pick areas.
  5. Under Which agents?, choose All agents or Choose agents.
  6. Choose Allow, or Deny.

Check it worked: it shows under Allowed and denied.

A deny wins over any allow. An allow adds nothing to an administrator.

Permissions and approvals explains areas and denies.

Turn off someone's sign-in

Before you start: you need to be an administrator, signed in as yourself. An administrator can make you one.

  1. Open Users and open the person.
  2. Open the ⋯ menu beside Edit.
  3. Choose Disable sign-in, then Disable sign-in again.

Check it worked: their page shows Disabled. Enable sign-in in the same menu turns it back on.

Delete account… in the same menu deletes the login but keeps the person, chats and usage. You can invite them again.

Permissions and approvals explains roles and sign-in.

Remove a person

Before you start: you need to be an administrator, signed in as yourself. An administrator can make you one.

  1. Open Users and open the person.
  2. Open the ⋯ menu beside Edit and choose Remove from Sunport….
  3. Read the list of what happens.
  4. Choose Remove from Sunport.

Check it worked: their row in Users shows Removed.

Their agents become yours and keep running. Their record stays, archived, with their chats and web usage.

Permissions and approvals explains roles and sign-in.

Set agent owners' access

Before you start: you need to be an administrator, signed in as yourself. An administrator can make you one.

  1. Open Settings › Access.
  2. Under An agent's owner gets, choose Chat or Chat and settings.
  3. Choose Save.
  4. Confirm with Lower to Chat, or Raise to Chat and settings.

Check it worked: the page says agent owners now get the level you chose.

It applies to every owner at once. Agents an administrator owns don't change.

How agents work explains owners and access levels.

Decide an approval

Before you start: the approval must be asked of you. Sign in as yourself, not with a narrower key.

  1. Open Settings › Approvals.
  2. Under Asked of you, read what the agent asks.
  3. Choose Approve or Decline.
  4. For a secret, type it and choose Save.

Check it worked: choose History. It shows Approved, Declined or Given.

Administrators also decide Clem's changes: Waiting for administrators opens them, and oo clem waiting lists them.

Permissions and approvals explains what waits for whom.

Choose how people sign in

Before you start: you need to be an administrator, signed in as yourself. An administrator can make you one.

  1. Open Settings › Sign-in.
  2. Turn Let members sign in with OpenOrange on or off.
  3. Turn Let people sign in with a code sent to their email on or off.
  4. For the owner, open Settings › Maintenance access.
  5. Turn Allow opening from the app on or off.

Check it worked: Saved. appears beside each switch you changed.

The owner's app opening turns off only once their login has a password or passkey. Members' link requests wait under Linked OpenOrange accounts.

Permissions and approvals explains each way to sign in.

Set a password or passkey

Before you start: you need your own login, not a key.

  1. Open Settings › Profile.
  2. Under Password, type your Current password, if asked, and a New password.
  3. Choose Set password, or Change password.
  4. Under Passkeys, choose Add a passkey and follow your device.

Check it worked: Password set. You can now sign in with it., Password changed. Your other devices are signed out. or Passkey added. You can sign in with it now. appears.

Changing your password signs you out on your other devices. Passkeys are added in the dashboard only.

Permissions and approvals explains each way to sign in.

Edit your profile

Before you start: you need your own login.

  1. Open Settings › Profile and choose Edit profile.
  2. Change Name, or choose Change image.
  3. Choose Save changes.

Check it worked: Profile updated appears.

A picture is a PNG, JPEG or WebP file, up to 3 MB.

Choose your theme and currency

Before you start: anyone signed in can choose these.

oo has no command for this. Choose them in the dashboard:

  1. Open Settings › Preferences.
  2. Under Theme, choose System, Light or Dark.
  3. Under Currency, if it shows, choose USD or RUB.
  4. Under Activity view, choose List or Map.

Check it worked: each choice applies as soon as you make it.

These are saved in this browser, just for you. Records and exports stay in USD.

Schedule updates

Before you start: you need Change settings (settings.write). Not an administrator? Ask one to give you See settings and Change settings.

  1. Open Settings › Updates.
  2. Under Automatic updates, keep Install updates automatically on.
  3. To limit when, turn on Only during set windows. Set each window's days, From and Until.
  4. Choose a Time zone.
  5. To pause, turn on Hold updates until a date and pick Resume on.
  6. Turn Install security updates at once on or off.
  7. Choose Save.

Check it worked: Saved. appears, and the summary says when updates install.

An update already running may finish. Update now doesn't follow your windows.

Data, privacy and updates explains how updates install.

Update your Sunport now

Before you start: you need Change settings (settings.write). Not an administrator? Ask one to give you See settings and Change settings.

  1. Open Settings › Updates.
  2. Under Update now, choose Update to followed by the version on offer.
  3. To be safe, turn on Snapshot every machine first.
  4. Choose Update now.

Check it worked: Update history shows it In progress, then Succeeded.

The dashboard and Clem restart, and each agent restarts in turn. New chat messages can't be sent until it has finished. Afterwards, oo update matches your oo to the Sunport.

While agents are working, the update waits until they finish. They are asked to finish or stop at a safe point. Install now (--install --now) installs at once and stops their work. Don't update (--cancel) drops the waiting update.

Data, privacy and updates explains how updates install.

Choose what's shared with OpenOrange

Before you start: in the dashboard, you need to be an administrator. With oo, See settings (settings.read) and Full control of the Sunport (sunport.root) are enough; an administrator can give you See settings and Full control of the Sunport.

  1. Open Settings › Data sharing.
  2. Under Optional sharing, turn a choice on or off.
  3. When you turn one on, choose Turn on to confirm.

Check it worked: the switch stays as you set it.

Always sent can't be turned off. OpenOrange needs it to run, bill and update your Sunport.

Data, privacy and updates explains each choice.

Set request retention

Before you start: in the dashboard, you need to be an administrator. With oo, See settings (settings.read) and Change settings (settings.write) are enough; an administrator can give you See settings and Change settings.

  1. Open Settings › Privacy.
  2. Under Keep request and response content, choose a period.
  3. Under Disk budget, choose the most disk it may use.
  4. Turn Administrators can view content on or off.
  5. Choose Save.

Check it worked: Saved. appears.

Content older than the new period is removed within the next quarter hour. Usage and billing numbers stay.

Data, privacy and updates explains what is kept.

Hold the keys yourself

Before you start: you need to be the Sunport's owner, signed in as yourself.

  1. Open Settings › Privacy.
  2. Under Keys, choose Download recovery file.
  3. Keep the file somewhere safe.
  4. Under Keys, choose the recovery file you just downloaded.
  5. In Hold this Sunport's keys yourself?, choose Hold the keys.

Check it worked: Keys says your Sunport holds its keys itself.

This can't be undone. Moving your Sunport to a new server may then need your recovery file.

Data, privacy and updates explains what the keys open.

Let OpenOrange into your server

Before you start: in the dashboard, you need to be an administrator. With oo, See settings (settings.read) and Full control of the Sunport (sunport.root) are enough; an administrator can give you See settings and Full control of the Sunport.

  1. Open Settings › Maintenance access.
  2. Choose Open access.
  3. Under How long, choose 1 hour, 24 hours or Until closed.
  4. For Until closed, tick I understand that access stays open until someone ends it.
  5. Choose Open access.

Check it worked: the page shows Open. End access now ends it early.

The same page shows the Server console password, for your provider's console. Each reveal is recorded in the audit log.

Data, privacy and updates explains maintenance access.

Export activity

Before you start: in the dashboard, you need to be an administrator. With oo, See users (people.read) is enough; an administrator can give you See users.

  1. Open Overview and choose the period.
  2. Choose Export people CSV.

Check it worked: your browser downloads a CSV file.

To export every charge, follow Export your charges.

Data, privacy and updates explains what your Sunport keeps.

Turn on backups

Before you start: you need Manage recovery (recovery.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See recovery, Manage recovery and Start jobs.

  1. Open Settings › Backups.
  2. Under Nightly backups (off-server), choose Turn on.
  3. Under a machine's Daily backups, choose Turn on.

Check it worked: The first backup runs tonight. appears, and the machine says when its daily backups are taken.

Both are charged to your prepaid balance. Turning either off deletes its backups, and can't be undone.

Data, privacy and updates explains each kind of backup.

Take a snapshot

Before you start: you need Manage recovery (recovery.manage) and Start jobs (jobs.create). Not an administrator? Ask one to give you See recovery, Manage recovery and Start jobs.

  1. Open Settings › Backups.
  2. Under the machine's Snapshots, optionally type a name.
  3. Choose Take snapshot.

Check it worked: the snapshot shows Being taken…, then its size.

A snapshot is charged by its size each month until you delete it. Each machine keeps a limited number.

Data, privacy and updates explains each kind of backup.

Restore a VM backup

Before you start: you need to be an administrator. An administrator can make you one. The VM must be running.

  1. Open Settings › Backups.
  2. Under the VM's Restore, choose a backup or snapshot.
  3. Choose Restore….
  4. Type the VM's name and choose Overwrite and restore.

Check it worked: the VM's Restore says it was restored from that copy.

Everything on the VM is replaced, and it restarts. A snapshot is taken first, which is the way back.

Data, privacy and updates explains each kind of backup.

Grow the server disk

Before you start: you need to be an administrator. An administrator can make you one.

  1. Open Settings › Server disk.
  2. Under Grow the disk, choose a New size.
  3. To apply it now, tick Restart the Sunport now so it takes effect.
  4. Choose Grow disk.
  5. Check the price, and choose Grow disk again.

Check it worked: the page shows the new size once the grow is done.

A bigger disk can't shrink again. A restart takes your Sunport offline for about 20 seconds. On Hetzner, a bigger disk comes with a bigger server: choose Move to and the server instead.

Data, privacy and updates explains what is charged.