Rust · 0.1.0

Instance settings

Manage instance-wide behavior without confusing it with personal preferences.

Administrator settings

The settings interface separates administrator sections from personal sections. Instance administration includes general/access policy, memo policy, storage, notifications, identity providers, AI providers and resource statistics. User preferences, personal tokens, tags and webhooks belong to their own sections. Change one policy at a time and verify it using a regular account.

Access is a separate decision

Instance access controls anonymous entry; memo visibility controls each memo's audience. The external instance URL identifies the origin and does not replace access policy. A share link is an explicit grant to a selected memo. Review sharing before assuming private instance access disables every existing link.

Settings that cannot be edited

An active deployment-file override can make a setting read-only through the application. Update the authorized deployment configuration and restart instead of trying to overwrite it repeatedly. Do not copy secret fields from a provider configuration into a support request.

Change one policy and verify it independently

For an instance-wide policy, use an administrator account and Settings → System. Record the current access and registration choices before changing them. Update the intended control and save; reload Settings to confirm it persisted. Then check the public entry point in a separate signed-out browser and the ordinary-account experience. A normal user should not acquire administrator settings access just because they are a space administrator. If Save returns FAILED_PRECONDITION, check whether the corresponding group is supplied by /etc/secrets and use the deployment owner’s restart process.