Settings and what it does not hold

Settings is the organization half of the account pair. It is a short page, and being honest about how short it is saves you hunting it for a control that is not there: one section does something, and the rest point at the pages that carry the rest.

What is actually on the page

Every section of the settings page

Section	What it does
The header	Names the organization you are in and your role in it. Neither can be changed here.
Read-only API tokens	Creates, lists and revokes the tokens an AI client uses. The only control on the page that changes anything.
Your own account	A link to your profile, which carries your name, address and Google connection.
Privacy and cookies	Links to the privacy centre and to the cookie settings page.

The token list is yours, and only in this organization

The query behind the list is filtered three ways: to the organization you are in, to your own user record, and to tokens that have not been revoked. Another member's token is never in your list, and neither is one you made in a different organization.

Fields the page fetches

Name, prefix, created date and last use

all four are read from the database for every token in the list

Fields the list shows

Name and prefix

the created date and the last use are fetched and then not displayed

Expiry the create form sends

90 days

fixed in the form; you are not offered the field

Creating and revoking

The form takes a name and nothing else. The value appears once, immediately below the form, and is never shown again. Revoking is a single control on the row, and it takes effect on the token's next request rather than at the end of a session. Why the value cannot be reprinted, what the token reaches, and the quota on issuance are all in personal access tokens.

Your role does not gate this page

The page asks for a signed-in session in an organization and nothing more. It does not check your role, so a viewer who cannot import a single row can still mint a token here.

That is consistent rather than a gap. The token carries the organization it was made in, not your role, and every token reaches the same read-only tools. It cannot do anything its holder's session could not already do. The boundary that matters is the organization one, and that is the subject of how organizations work.

The page guide on this page overstates it

What settings does not do

It does not rename the organization. It does not manage members: that surface is the organization page, and it is read-only too. It carries no notification, theme or language preferences; the theme control sits in the workspace header rather than here. There is no billing or plan section.

It also does not change where your organization thinks it is. Those values are written once, when the workspace is created, and no page updates them afterwards.

Values fixed when the workspace was created

Value	Where it came from
Organization name	Your email address up to the at sign, with the word workspace appended
Slug	That name, lowercased and hyphenated, with a short random suffix so two workspaces cannot collide
Country, region and city	Inferred from the request headers of the request that created the account
Timezone, locale, currency and measurement system	Derived from that same inferred location

If one of those is wrong, nothing on this site corrects it. That is worth knowing before you read a currency on a report and assume somebody chose it.

Where the rest lives

Your own name, address and sign-in methods are on your profile. Export and data-rights requests are in the privacy centre, described in your data and privacy. Consent for analytics and advertising is neither of those; it is on the cookie settings page.