Settings.

Account and workspace settings live at /settings on auth.bsns.cc. Personal cards are visible to every signed-in user. Company, team, billing, branding, onboarding, audit, support reports, business creation, and account closure are limited to workspace admins.

Profile, security, and personal tools

• Your profile controls display name, personal timezone, calendar details, and appearance across the suite.
• Security manages passkeys, TOTP authenticator apps, recovery codes, and password changes where a password is present. A new account has a seven-day MFA grace window unless the workspace is an admin-created demo. Google or Apple sign-in already satisfies the second-factor requirement.
• Impersonation activity shows when an administrator used View as to open apps as you. Admins can review the workspace-wide history there.
• API tokens creates and revokes personal access tokens for scripts and integrations. Treat a token like a password.
• Support notifications controls which support issue updates reach your notification inbox.

Team, seats, and app roles

Settings › Team invites a teammate by name and email. The link is emailed directly, lasts seven days, and can be resent from the pending row. Choose a full or light seat when inviting. The new membership starts with that seat class’s default roles across the apps subscribed by this business.

After the invitation is created, an admin can use the same page to enable or disable each app and choose its role. Removing somebody ends their access to this business without deleting their identity or their access to other businesses. If a full-seat invite exceeds the package’s included seats, the page asks the admin to confirm the added seat charge before sending it. See Roles, seats, and permissions for the current matrices.

Company, billing, and additional businesses

Company profile holds the business and legal names, EIN, address, phone, contact details, and company timezone. Billing shows the current plan, trial or renewal timing, seat charges, payment information, and the Stripe billing portal.

An existing workspace admin can use Add a business to create another separate tenant from the auth portal. It does not require a new account or an invitation code. See Working across multiple businesses for pricing and membership behavior.

Branding and onboarding

Branding controls the workspace handle, logo, display name, and login-page brand colors. Onboarding holds the first-run checklist for the apps and configuration provisioned to this business; an admin can dismiss it and return later.

Product-specific settings appear inside the owning app. For example, Work holds notification digests, calendar and booking connections, email delivery, imports, and the private Gmail pilot; Hive holds workspace shape, vocabulary, locations, payments, shipping, storefront, and procurement settings. Ask Wren “where do I change …” to search the settings directory and get a real link.

Audit and support reports

Audit logs cover privileged activity across the business, including invitations, access changes, View as sessions, and settings changes. Support reports lets admins review private problem reports filed by their team and any linked public issue.

Tenant admins with the View as grant can open work as an eligible non-admin teammate from /teams/view-as. The session is bounded and audited; see Tenant admin guide.

Demo data and closing a workspace

Demo data appears only on admin-created demo workspaces. It can load or clear seeder-owned sample records, or convert the workspace to live mode. It is not part of the normal self-serve trial path.

A workspace admin can use Close accountto stop the next subscription renewal and schedule permanent deletion. The workspace becomes read-only immediately and has a 30-day undo window before deletion; an already-paid period is not prorated or refunded. This closes the selected business, not the person’s identity or unrelated businesses.