Workspace Settings Overview

One-stop tour of every Workspace settings surface in Sparko.

Sparko's Workspace settings are grouped into three sections you'll see in the left sidebar when you open them. This guide walks through what each page controls and where to find it.

---

Opening Workspace settings

Open the product switcher at the top of the sidebar and choose Workspace settings (visible only if you have admin permissions). People and Legal also have a Settings entry in their own sidebars that opens the same place. The sidebar swaps to Workspace settings: the left rail now shows only settings pages, and under the product switcher a Back to link (for example, Back to People or Back to Legal) returns you to the product you came from.

The Workspace settings sidebar is grouped into three sections:

Section	What lives here
Workspace	Company · Entities · Roles and access · Billing and plans · Security and sign-in · Integrations · AI · Audit and data
People	General · Contract templates · Departments · Custom fields · Onboarding · Recruiting · Performance · Compensation · Time and leave · Engagement · Career
Legal	Legal settings

---

General

Company Settings

Five company-wide settings, each on its own page:

• Company (/admin/workspace/company). Company name, logo, size, timezone. Uploading a logo opens a crop and zoom step so it sits right in the sidebar and on documents. PNG, JPG, GIF and WEBP up to 5 MB. The file is checked by its actual contents, so renaming something won't get it through.
• Security and sign-in (/admin/workspace/security) and Privacy (/admin/workspace/audit/privacy). Security and sign-in holds Authentication (MFA enforcement, password policy, session timeout). Session timeout is how long people stay signed in on the web and in the mobile app before signing in again, from 1 hour up to 720 hours (30 days). The field shows the length in days as you type, for example "720 hours = 30 days". Under 8 hours you see the warning "Sessions under 8 hours sign people out during a working day." You can still save a shorter timeout. A new timeout applies the next time someone signs in. Two people for payroll is on by default: the person who built or last changed a payroll run can't finalize it. If only one person can run payroll, they can still finalize, and that is logged. Privacy holds Data Protection (retention policy, privacy & terms URLs) and Employee Data Visibility (equity toggle, pay transparency tier).
• Modules (/admin/people/general/modules). Per-module enable/disable. Use this to hide a module from your sidebar if you're not using it (for example, disable Recruiting if you don't hire externally through Sparko).
• AI (/admin/workspace/ai). Master switch for AI features plus per-module AI toggles (Recruiting AI, Performance AI, and so on). Toggling the master off hides ALL AI features regardless of per-module state.
• Workflow (/admin/people/general/workflow). Skip-level approval delegation. When on, a senior manager can approve requests (PTO, comp changes) on behalf of any manager in their reporting chain, which is useful when a manager is out of office. The audit log records both the approver and the bypassed manager.

Save behavior: The "Save changes" button at the bottom of the page only sends fields you actually changed. The dot indicator turns amber when you have unsaved changes.

Accounts

In People > General, choose Manage account access to open Members. Use Invite member for one person, or Send staged invitations for imported people who have not been invited yet. Existing invitation URLs also open Members.

Use the account-status tabs, Filter and Search members to find a person, then click their name or Manage. The member drawer shows sign-in information and the account actions your permissions allow. An activation count alone does not mean every account can sign in.

• Unlock account appears for locked, active accounts when you have account-unlock permission. It clears the lock without changing the password, passkeys or sign-in methods.
• Send password reset link sends a one-hour link to the saved sign-in address when password sign-in is enabled and you have member-management permission. The member chooses the password. Sparko reports whether the email provider accepted the message; acceptance does not guarantee inbox delivery.
• Recovery cannot reactivate an account, enable password sign-in, recover an account with greater access than you hold, or change your own account. Your own record links to account security settings instead.

Required two-factor enrollment still applies. Administrator and recipient limits are separate from the public forgot-password limit. If sending succeeds but refreshing the drawer fails, use Refresh account status; that retries the status lookup without sending another email.

Privacy: colleagues in other entities

Where: Privacy, Employee Data Visibility.

Under Colleagues in other entities, set Directory, Org chart and Profile basics separately. Changing one keeps the other two as they are. Select Save changes to apply your choices, or Discard to restore the saved settings. What stays private explains that these settings never show pay, reviews, leave or documents: those follow roles only.

• Your own reporting line always shows: your managers and your reports, in every entity.
• With one entity the settings change nothing, and the page says "You have one entity, so everyone sees everyone."
• When you add a second entity and have not chosen yet, Sparko turns all three off. Turn on the places where your entities work as one team.
• These controls are on Growth and above. On Core they show one "Available on Growth" notice.
• You need permission to manage workspace settings to change them. After a downgrade, your saved choices stay in force and can no longer be changed.

Entities (/admin/workspace/entities)

An entity is a company you employ people or sign contracts through, such as "Acme Pte. Ltd." in Singapore. Payroll groups pay and bank files by entity, and e-sign completion certificates print the entity's legal name, registered address and authorised signatory.

Each entity has a display name, legal name, registration number, registered country and default currency, plus its signing details:

• Authorised signatory. Who signs for the company by default. Under Signing, choose Member or Outside the company.
  • Member: pick from the people who can sign for the company, so give someone the sign-for-company permission first. When sending, the sender may delegate to another person who can sign for the company.
  • Outside the company: a director or other signatory who doesn't use Sparko. Enter their full name, email and title. They get an email with a secure link and a one-time code each time a document needs the company's signature. The entity list marks them External, and the signing record prints them as "Company signer, external". Only someone who can sign for the company in every module can name or change an outside signatory, and the email can't belong to someone in the workspace (choose them as a member instead). While an employment contract waits for the outside signatory to sign, void it before changing them; when they change, their open signing links stop working and the sender is notified. When you prepare a document, Sparko shows the email the signing link goes to.
• Signatory title, such as Director, printed under the signature.
• Registered address: address lines, city and postal code; the registered country is the country above.
• Standard weekly hours (EU countries only). Hourly pay in pay information replies and the EU gap report uses this when a person has no contract hours.

Add entity and Edit open a modal. The display name, legal name, registered country and default currency are on top. The registration number, signing details and registered address sit under Advanced, a fold that stays shut until you open it. Its summary line shows the registration number, who signs and the city.

Everyone with admin.entities.view sees the page. Editing needs admin.entities.manage or compensation.paying_entities.manage.

Plan limit. 1 entity on Core, 5 on Growth, 20 on Business, unlimited on Custom. A workspace without a People plan, such as a Legal-only workspace, holds one entity.

Members (/admin/workspace/members)

Everyone who can sign in to your workspace, with their roles and which products they can use. One table, 25 members a page, with scope tabs across the top (All, Active, Invited, Not invited, No login, Deactivated, each with its count), a pill search by name or email, and a Filter button for product access, role, sign-in method and locked accounts. On a phone the table shows the member and their status; open the member for the rest.

• Invite member opens a short form: first name, last name, work email, an optional job title and the roles to start with. The invitation email carries a sign-in link.
• Send staged invitations appears when the Not invited count is above zero and sends every pending invitation at once.
• Manage (or the member's name) opens the member drawer: their roles grouped by product, their product access, and their sign-in account with Send password reset, Resend invitation and Deactivate sign-in or Reactivate sign-in. Deactivating ends every session and switches the login off without touching the employee record; the last Super Admin cannot be deactivated or demoted.
• Product access lists the products your workspace holds. Workspace owners always have every product. Changing a member's products is switched off until the next platform update; until then new members receive the products you hold.

You can only grant roles you could hold yourself, and promoting someone to Super Admin needs access to every product the workspace holds. Viewing the page needs admin.members.view; inviting, changing roles or access and deactivating need admin.members.manage.

Integrations (/admin/workspace/integrations)

One page for everything Sparko connects to. Seven tabs:

• Apps. The directory. One card per connection (Slack, Microsoft Teams, Linear, Notion, Public API, Webhooks) with its current state, and a jump to its tab.
• Slack. Post Sparko notifications to Slack channels.
• Teams. Send Adaptive Card notifications to Microsoft Teams.
• Linear. Lets the assistant reference recent Linear work activity.
• Notion. Lets the assistant cite your own Notion policies.
• API Keys. Read-only keys for the Sparko public API. Needs admin.api_keys.view.
• Webhooks. Signed event notifications to your endpoints. Needs admin.webhooks.view.

Each tab has its own address, such as /admin/workspace/integrations/slack, /admin/workspace/integrations/api-keys and /admin/workspace/integrations/webhooks. The API Keys and Webhooks tabs only appear if you hold their permission.

---

Module Settings

Each module has its own admin page that surfaces only the company-level policy for that module. Module-internal config (individual PTO policies, individual review cycles) lives inside the module, not here.

People (/admin/people/general)

• Field visibility. Four DEI toggles (ethnicity, gender, veteran status, disability status). Today these save but the backend filter isn't fully wired yet (see roadmap R3); a callout on the page makes this transparent.
• Holiday calendars. Enable holiday calendars, plus a link to the in-module page where you assign calendars to employees.
• Onboarding Settings (/admin/people/onboarding). What runs between a sealed contract and day one: when the login invite goes out, how each plan starts (AI from the role, a template or blank), who owns and approves it, buddy suggestions, what the pre-start page shows, default equipment kits and who gets equipment requests, the day-one tasks, and the first-day details. Google Workspace and Slack accounts are IT tasks; Sparko does not create them. See the People module guide, "Onboarding settings".
• Onboarding Templates (/admin/people/onboarding/templates). The reusable plan template library. See below.

Contract templates (/admin/people/contract-templates)

Employment contract templates for each of your entities, for work in any country. All templates sit in one table (Template, Entity, Contract types, Source, Status, Last edited). A line under it says how many entities have no template, with a Generate button. Generate one with Sparko AI, upload a Word document, or start blank; review every clause and the statutory checklist on the Checks tab, then publish. Needs the Manage Employment Contract Templates permission. Templates are general information, not legal advice. See Employment Contracts.

Documents and ID (/admin/people/documents-and-id)

Which permits and IDs each paying entity must hold, and when reminders go out. It shows only if you can manage identity documents.

• Required documents. A table with one row per document type and one column per paying entity. Switch a toggle on to make that document required for the entity's workers. "Not used" means the entity has no such document.
• Reminder schedule. Toggles for 90, 60, 30 and 7 days before expiry and on expiry.
• Advanced. A fold that stays shut, with a one-line summary. Inside, Recipients (HR, Worker, Manager toggles) and Renewals and checks, three rules marked Always on: workers upload renewals and HR verifies them, lapsed permits hold assignments and shifts, and the WPS file is blocked when it names a lapsed permit.

See Documents and ID.

Career (/admin/people/career)

• Structure. The level vocabulary for each ladder, the job families those ladders belong to, and the map from each job title to a family, track and rung. Every edit here is reviewed before it is written: you get the list of changes, what each one touches (job titles, people, bands, competency cells) and the reason any change cannot run, and nothing is saved until you choose Apply.
• Employee report visibility. Three toggles controlling what each employee sees on their own career intelligence report: readiness score, time-to-ready estimate, AI narrative.
• Skill graph automation. Auto-build skill graph when a new hire is created.

The level vocabulary

Structure opens on three ladders, one per track. Sparko starts you with L1 to L5 on the individual contributor ladder, M1 to M4 on the manager ladder, and nine rungs on the Leadership ladder (Head, Senior Head, Associate Director, Director, Senior Director, Associate VP, VP, Senior VP, CxO). They are starting points: rename any rung and every career path that uses it is renamed with it.

• Add level appends to the end of a ladder. A level cannot be inserted in the middle, because a rung's position is its identity and inserting one would renumber everyone above it. Moving someone between levels is a redesignation, not a reorder, which is why Structure offers no drag-to-reorder.
• Remove is offered on any rung, and refused with a count when anyone or anything still sits on it. The review screen tells you what is in the way before you commit.

Job families

A job family is the discipline a ladder belongs to, and it is what a salary band is priced against. Each row carries a Manager track switch: turn it on and the family can carry manager-track titles as well as individual contributor ones. Whether a family is a leadership family is shown when you open it, and is not a switch.

Action	What it does
Add family	Creates a new family.
Rename	Renames it everywhere at once: titles, ladders and bands follow.
Merge	Folds another family into this one. Its job titles, ladders and bands move across, and the family you folded in is retired rather than deleted. If the merge had to put a retired rung of this family back in use, Sparko tells you which.
Split	Moves the job titles you tick into a brand new family. Everything you did not tick stays where it is. Only titles already mapped to the family are offered, so a typed name cannot silently move nothing.

Job titles

The Job titles block is the map from the titles your people actually hold to a family, track and rung. Each row shows the family, the track, the level, where the mapping came from (HR, Setup, Auto or Backfill), its confidence where one was recorded, and how many people hold that title today.

The block opens on Unmapped whenever any title has no real family, because that is the work to do; All shows everything. Change family moves a title: pick the new family, and if the title's track is not one that family accepts you are asked to pick a track it does. The level is cleared when a title moves, because the old level belonged to the old family's ladder, and the new family's rung is set the next time someone is assigned.

Recent changes and Undo

At the bottom of Structure, Recent changes lists the changes that have been applied, newest first: when, who made it, what it did, and whether it is still in place. 20 at a time, with Show more for older ones. Changes made by the AI assistant appear here too, credited to the person who approved them.

A change shows an Undo button when it can still be reversed. Choosing it shows what will be put back and asks you to confirm. If a later change stands on the one you are undoing, Sparko names that later change and asks you to undo it first, rather than leaving your structure half-reversed. A change that has already been undone keeps its row, marked Undone, and the change that undid it is listed in its own right.

Job families, the job title map, Recent changes and Undo need the Manage Career Framework permission. Renaming, adding and removing levels needs Manage Career Config. Reading the job title map needs View Career Config. The whole Structure section needs Growth or above.

Note: Career Settings exposes only the 4 columns that are actively consumed in code. The other 7 columns on the underlying CompanyCareerConfig table aren't wired yet. They will appear here when their consumers ship.

Performance (/admin/people/performance), slim

• Manage Cycles deep-link. Per-cycle cadence and templates live in the Performance module, not here. Click "Open" to jump there.
• Cycle automation. Auto-create next cycle toggle.
• Team highlights per manager review. 3, 5 or 7. How many of their reports' achievements a manager may carry into their own self-review. Ranked by impact; the manager can re-order.
• Calibration. Enable toggle, 9-box vs 4-box grid type, AI suggestions toggle.
• Compensation integration. Whether comp changes are in-scope by default for new cycles.

Compensation (/admin/people/compensation)

Compensation settings has these pages in its menu: General, Salary bands, Payroll, Payroll rules, Compliance and Expenses. General shows four things up front and folds the rest under Advanced.

• Structure. Where bands are priced, the currency they convert to, and the rates that do it. See below.
• Transparency and approvals. The pay transparency tier (Off, Band only, Full range, Exact position) and the Number of approval levels (1 to 5, in order: Manager, Reporting head, HR, Finance, Head of People).
• Advanced. A fold that holds the rest:
  • Equity module. Adds the Equity tab in Compensation for managers and HR.
  • Publish ranges on public job postings. Postings where the law requires a range always show one.
  • People per group. The smallest group shown in pay replies, from 3 to 50. A smaller women's or men's group in a pay information reply is withheld, and the reply says why. The same size hides the gap for small categories in the EU gap report. See Compensation: Pay information requests (EU).
  • Manager visibility delay (days). Days a newly hired manager must wait before seeing their team's compensation (0 means off). Covers every team-comp surface: salary bands, the Compensation Hub, team compensation views, the merit worksheet, outcome letters, and Total Rewards. HR Admin always sees full comp regardless of the delay.
  • Vesting templates. A count of your vesting schedules (4 years with a 1 year cliff, and the like) and Create to add one. Each template can be deleted, except the default.
  • Comp approval policies. A count of your per-change approval chains and Create to add one. Each policy can be deleted, except the default.
• Payroll. Pay groups, with links to Workspace settings, Entities, to Payroll rules and, where you have access, to the Books payroll posting setup.
• Expenses (/admin/people/compensation/expenses). Approval limits, receipt rule, claim window, how approved claims are paid, finance approvers, expense categories per country and mileage and per diem rates. See Compensation: Expenses.

Structure: band geography, base currency and FX rates

Band geography decides the grain every salary band is priced at. There are two choices, and the section tells you how many office locations you have before you pick:

• Per office location. One band per level and office. A location with no band of its own falls back to the company-wide band for that level.
• Company-wide. One band per level for everyone, wherever they sit.

Going company-wide is refused while any level still carries more than one live band, because Sparko will not pick a winner for you. The refusal counts the levels, names the first few, and asks you to merge each down to one band first.

Base currency is the currency every rate is quoted against, and the one the matrix converts into when you pick a display currency. Only a currency that already has a rate can become the base, so add the rate first.

Under the base currency, one line counts your rates, for example "3 currencies · rates from 1 Oct". Manage rates opens the Policy FX rates drawer. It is your own rate table, not a live market feed. Each row is a currency, its rate to your base currency, and the date it takes effect. Add rate (currency, rate to base, effective from) adds one, and Retire removes one. Show history brings back rates that a later rate replaced. Sparko refuses to remove the last rate for your base currency, since every conversion reads it. With no rates at all, bands simply stay in their own currency and the matrix shows local figures.

Structure is part of the salary bands feature, so it is Business and above. On Core and Growth the section shows a locked card in place of the controls. Where it is available, changing anything in it needs admin.settings.manage, and reading it needs admin.settings.view.

Pay groups

Where: Compensation, the Payroll tab, Pay groups.

A pay group says how often its people are paid and when hours stop counting for a run. Groups are shown in one card per entity. Add pay group asks for a name, an entity, a frequency, the hours cut-off day (monthly groups), the approval cut-off day and the pay date. Hours approved after the cut-off are paid in the next run, never twice and never lost.

Payroll rules

Where: Compensation settings, Payroll rules. The Payroll tab also links to it.

Payroll rules are the statutory contributions, tax and overtime rules Sparko applies per country. Pick a country in the country search at the top. The subtitle states the country's facts, and Country rule beside the search opens the country's own rule. One table lists the rules in groups: Minimum wage, Contributions, Overtime, Service benefits and Switched off. Its columns are Contribution, Party, Rate and Verified. Add minimum wage adds a minimum wage row.

• Source. Sparko rows come from official sources and link to them. Your version rows are your own edits.
• Verified. A rule marked To check still computes, and the payroll run review shows Rule to check on the lines it touches.
• Open a rule by clicking its row. Edit saves your own version, and Sparko's row stays for reference.
• End stops your version from a date. Revert to Sparko's goes back to Sparko's row. Mark verified records that you checked a version marked To check.
• Add a country, at the end of the country search, adds a country. When Sparko has rules for it, they are copied in. When it does not, Draft with Sparko AI drafts them for you to check against an official source, or you can add them by hand.

Recruiting (/admin/people/recruiting)

One page, five tabs along the top. The tab is mirrored in the URL (?tab=jobs).

• General. AI candidate-screening toggle (gated by the AI master switch), interview-duration and candidate-retention defaults, and short-code job URLs.
• Jobs. Job posting approval, and the interview pipeline template library (create and edit in a modal).
• Offers. Offer approval chains and the offer letter document template.
• Email Templates. Candidate emails, the transactional emails, with per-tenant overrides.
• Careers Page. The full public careers page builder.

Offer letter template

When an offer goes to a country with no benefits block yet, Sparko drafts one in the background, and Generate with AI drafts one for a country the catalogue does not cover. A generated block is marked AI-generated with the date it was written: check it before you send offers. You can edit it like any other block.

Onboarding (/admin/people/onboarding/templates)

The onboarding template library. Onboarding settings sit next to it at /admin/people/onboarding.

• Search and category filters (Engineering / Sales / Leadership / Other) with counts.
• One card per template: category, description, task count, group count, day span, how many times it has been used, and when it was last edited.
• Use. Creates a live plan for a named hire from a start date, then opens the plan editor.
• Edit. Opens the template in the plan editor.
• Kebab menu: Rename, Duplicate, Delete. Deleting a template does not affect plans already created from it.
• Import from plan. Copies an existing plan's groups and tasks into a new reusable template.
• New template. Starts a blank one, then opens the plan editor to add its tasks.

Creating needs onboarding.plans.create; editing and using need onboarding.plans.edit.

Time & Leave (/admin/people/time-leave), slim

PTO policies and leave types are configured in the Time & Leave module, NOT here. This page is approval workflow defaults only:

• Default approval chain. 4-card picker: Manager only / Manager then HR Admin / Manager then Skip-level / Custom (per-policy).
• Overrides & thresholds. Per-leave-type override toggle, auto-approve threshold in days (0 disables it).

Engagement (/admin/people/engagement), slim

Pulse cadence and templates live in the Engagement module. This page is company-wide admin policy:

• Pulse surveys. Master enable, opt-out allowed.
• Recognition. AI suggestions toggle. Recognition posts are always visible company-wide; there is no per-company default to configure.
• Announcements. Default channel, audience scope, require-approval toggle.

---

Security & Compliance

Roles & Access (/admin/workspace/roles)

The RBAC Studio. Three tabs, each with its own address under /admin/workspace/roles:

• Studio. One roles table with System roles and Custom roles tabs, a Filter button and a search box. Opening a row shows the role's permissions grouped by module in a drawer. The people count on a row opens a drawer listing who holds the role.
• Employee Assignments. Overview by role with bulk-assign actions.
• Assignment Rules. Visual when/then rule cards for auto-assigning roles based on employee attributes such as department or role level.

Separate guide: see roles-and-permissions.md in this folder for the full RBAC model walkthrough.

Security and sign-in (/admin/workspace/security)

One page in three cards. Sign-in policy holds the password rules, the session timeout, the two-people-for-payroll switch and the MFA requirements. Google sign-in switches Google sign-in on or off for the whole workspace; members with a matching saved work email can then use their Google account. SAML single sign-on is where you connect your identity provider: see the Single Sign-On section of integrations.md in this folder for the walkthrough. Switching Google or SAML on needs admin.sso.manage and your authenticator code.

Audit Logs (/admin/workspace/audit) and Data Requests (/admin/workspace/audit/data-requests)

Both live under Audit and data in the Workspace section:

• Audit Logs. Security events, plus the RBAC audit trail at /admin/workspace/audit/rbac (role assignments, permission grants and revokes). Filter by entity type or action.
• Data Requests. GDPR/CCPA data subject requests in a 3-column kanban (Pending / In Progress / Completed).

The Data Requests queue and the retention policies come with People Business and above, or with Legal Growth and above. A Legal-only workspace on Legal Growth has them without a People plan. Answering a single request (create, view, execute or cancel) is open on every plan. On a plan without the queue, the locked card names the plan that adds it: Business when your workspace has People, Legal Growth when it has only Legal. A Legal plan adds only the queue and retention policies: the bias and governance audit and the workspace compensation access audit stay with People Business.

Each has its own address, so the URL determines which one is open.

What a deletion request erases. After the 30-day cooling-off period, Sparko:

• Anonymizes the person's employee record: name, contact details, address and emergency contacts.
• Deletes every document on their profile, and the stored file behind it. That includes uploads, certificates and filed payslips. Your payroll run history keeps the pay record itself.
• Anonymizes the candidate record they were hired from, and deletes their résumé file.

Legal contracts are kept. They are your company's records, not data about the person.

If a file could not be deleted, the request still completes, and badges under its status show how many files are left. Hover, focus or tap a badge to read the full note:

• 2 files queued: the files are not deleted yet. Sparko retries the delete every night, and the count goes down as files are deleted.
• 1 file needs support: Sparko can't delete that file on its own, so contact support.

When the badges are gone, every file is deleted. Until then, don't tell the person their data is gone. The audit log records the request as Partial.

---

Sidebar Preferences

The profile dropdown menu (click your avatar bottom-left) includes two per-user preferences:

• Sidebar grouping (the layout-grid icon). Toggle between section labels (default) and a flat list with dividers only. Per-user. Doesn't affect what other users see.
• Theme. Three-button segmented control: ☀ Light / ◐ Auto (follow OS) / ☾ Dark. Auto means your sidebar adapts to your OS-level dark mode preference; explicit Light or Dark overrides the OS.

Both preferences are saved to your account, not just your browser, so they follow you when you sign in on a different device.

---

What's NOT in Workspace settings

The following surfaces are NOT admin settings even though they sound like they should be:

Surface	Where it actually lives	Why
Individual PTO policies	Time & Leave module → Manage Policies	Per-policy editing is module-internal; admin only sets defaults.
Individual review cycles	Performance module → Review Cycle Management	Per-cycle config (cadence, template, scope) is module-internal.
Individual pulse surveys	Workspace settings → Engagement → Pulse cadence (/admin/people/engagement/pulse)	Recurring pulse cadence + question set, admin-configured.
Onboarding plans	Onboarding module → Plans	Plans are per-hire instances; admin sets how plans start, who approves them and the default length.
Specific candidates / interviews	Recruiting module	Per-candidate data is module-internal.

This separation is intentional: admin settings = company-wide policy that applies to every instance; the modules own the instance-level data.

Billing uses People, Legal and Books tabs in the Settings navigation. Each shows its own product plan or availability; shared payment details, invoices and contacts are under Workspace billing details. Books self-serve billing is not available yet. Viewing billing does not grant permission to change plans, start trials or edit billing contacts.