Profile

Manage your personal account settings.

Account Information

Personal Details

• First Name: Your first name
• Last Name: Your last name
• Email: Login email (cannot be changed)
• Phone: Optional contact number; see Phone number below

Update Profile

1. Edit fields
2. Click Save Changes
3. Changes apply immediately

Phone Number

The phone field is a country-aware picker so you don't have to type the country code by hand:

• Pick your country from a searchable dropdown showing each country's flag, name and dialing code. Search by country name, ISO code, or dialing code. Your country is pre-selected from your browser locale (you can change it).
• As-you-type formatting: the number is formatted for the selected country as you type, and the placeholder shows a real example number for that country.
• International form, no trunk prefix: the field holds the number as it is dialled from abroad, because the dial-code chip beside it already supplies the country. Turkey reads 501 234 56 78 rather than 0501 234 56 78, the UK 7400 123456 rather than 07400 123456. A trunk digit you type is dropped for you, and the same digits come back after a reload. Where a leading zero is a genuine part of the number rather than a trunk prefix, it is kept.
• Changing country re-formats what is already in the field against the new country's rules, so a number is never left half-composed from two plans.
• Validation: the number is checked against the selected country's rules. An unreachable or malformed number shows an inline error on blur and blocks saving. The field stays optional, so leaving it empty is fine.

Internally the value is stored as a single international (E.164) number, so it works consistently regardless of the country you picked.

note

Timezone is set during onboarding and is not editable on the Profile page.

Security

Last Sign-in

The Security section opens with a Last sign-in banner showing when your account was last authenticated, to the minute. It is drawn from your account's audit history, so it reflects the sign-in itself rather than your current session.

Check it whenever you return to the portal: a timestamp you don't recognize is the earliest signal that someone else has your password. If you see one, review Active Sessions below, sign out everywhere, and change your password.

If no sign-in has been recorded yet, the banner shows a dash rather than a date.

Password

Change your password:

1. Enter current password
2. Enter new password
3. Confirm new password
4. Click Update Password

Password requirements (advertised before you submit):

• Minimum 8 characters
• Mix of upper- and lower-case letters
• At least one number
• At least one special character
• No more than 72 UTF-8 bytes (long passphrases with multi-byte characters count per byte, not per character)

If a submitted password does not meet the policy, the form returns a single message (Password does not meet security requirements.) without spelling out which rule failed. This applies to password change, password reset, and invite acceptance flows.

Passwords are used exactly as you type them: leading and trailing spaces and special characters are preserved in login, invite acceptance, and password reset. If sign-in fails, check for accidental whitespace from copy-pasting.

Active Sessions

Active Sessions lets you "Review devices that can refresh access to your account."

Each entry names the device and shows when it was last used, along with the originating IP address where one is known. The session you are currently using is marked This device.

Two controls manage them:

• Sign out sits on every other session's row and revokes that session immediately. Any open browser using that session is signed out on its next request. The current session's own button is disabled; use the account menu to sign out of the device you are on.
• Sign out everywhere revokes every session except the one you are using.

If you spot an unfamiliar device or an IP address you don't recognize, sign that session out and change your password.

note

Log Out in the account menu ends only the device you are using — your other devices stay signed in. Use Sign out everywhere when you want to end them all.

Revocation is immediate at every layer: a revoked session's access token stops working on its very next request rather than remaining valid until it would otherwise expire.

Linked accounts

If your platform has single sign-on configured, a Linked accounts card lets you connect Google or GitHub to this account and use it to sign in.

• Link takes you to the provider and returns you here. The provider must vouch for this account's own email address, verified — an account carrying a different address is refused, and the message names the address that was expected.
• Unlink removes a provider. If it is your only way in (no password set, one linked provider), the button is disabled with an inline explanation rather than failing after you press it.
• Only providers your administrator has enabled appear here.

See Signing In for the sign-in side of this.

Legal & consents

If your operator has published agreements and you have made any decision about one, a Legal & consents section appears at the foot of the page. It is the record of what you agreed to and when.

The section is absent entirely when there is nothing to show, which is every account until an operator publishes a document. If the record cannot be read the section still renders, saying "Your consent history could not be loaded." with a Retry — "we could not check" is not the same statement as "you have agreed to nothing".

What each entry shows

Each agreement is listed with its current standing decision on top: the wording, the version, the date, and the screen the decision came from.

Where it came from	Reads as
Accepting an invitation	at sign-up
Onboarding after a Google/GitHub sign-in	at sign-up (single sign-on)
The re-consent screen	when asked again
This page	from this page

The record is append-only: changing your mind adds an entry rather than editing the one before it. Where more than one decision exists, an Earlier decisions list underneath holds the rest, oldest kept exactly as it was recorded. Links your operator put in the wording are still live here, so a document can be re-read at any time.

Accepted, declined, withdrawn

• Accepted — you ticked the box.
• Declined — you left it unticked. Something never granted.
• Withdrawn — you had accepted it and later turned it off.

Turning an optional consent on or off

Optional agreements carry a switch. Flipping it writes a new entry and re-reads the record; the previous entries keep their own timestamps and are never touched.

Required agreements show a Required chip and no switch. They are a condition of holding the account, so ending one is an account-closure conversation with your operator rather than a toggle here.

An agreement your operator has since retired still shows the decisions you made about it — the record outlives the document.

See Legal Agreements for the registration and re-consent screens these entries come from.

Preferences

Display

• Theme: Light or Dark, toggled from the portal header
• Background motion: the header's freeze button stops the animated backdrop; the choice is stored per device. See Topbar Controls

Account Details

The profile page also shows read-only account details: your organization name, role, member-since date, and your Organization ID and User ID, both copyable.

Daily Spending Limit

Set a personal daily cap on what your own API usage may cost. When the limit is reached, further requests are blocked until the next day.

Control	Purpose
Effective Limit	The limit currently in force, and where it comes from
Set Custom Limit	Enter your own daily figure in USD
Reset to Default	Clear your custom figure and fall back to the organization or platform limit

The source of the effective limit is labelled Custom Limit, Organization Limit, or Platform Default. Your custom figure cannot exceed your organization's limit.

For how the limit hierarchy resolves, what happens when a cap is hit, and the alert thresholds, see Cost Limits.

tip

A daily limit on your profile covers your usage across all your keys. To cap a single integration instead, set a Daily spend cap on that API key.