Organization settings
General
The organization's name appears in the workspace switcher and on public form pages that have not set their own branding. Its logo is the fallback for every form and app that leaves the logo field blank — set it once here rather than on each of thirty forms.
Limits
| Limit | What happens at the ceiling |
|---|---|
| Forms | Creating another is refused with a message naming the limit. Existing forms are unaffected. |
| Responses per month | Further submissions are refused until the month rolls over. Counted across every form in the organization. |
| Dropdown lists | Creating another is refused. Platform lists do not count towards it — they are not yours. |
Dropdown lists
Organization → Dropdown listsis the workspace's dictionary: your own lists, plus the platform lists available to everyone. See Dropdown lists.
Assistant usage
Admins can see how much the AI assistant is being used in their organization under Organization → Assistant usage: questions, cost, and a chart over time, broken down by team (click a team to see its people), person, model or day. A bar shows how much of the month's assistant allowance has been used. It is for visibility, not a spending cap.
The audit log
Audit log records who did what and when: forms created, published and deleted; members invited, promoted and removed; settings changed; dropdown lists imported. It also covers teams and projects, sharing, webhooks, exports, and the organization itself — changing its settings or (for the platform team) suspending it.
Sign-ins are recorded too: each successful sign-in with the time, the person and where it came from, and failed attempts (at most one entry a minute for the same account, so an attack cannot bury everything else). Passwords, access tokens and invitation links are never written into the log — only what changed and who changed it.
It is append-only. Entries are never edited or removed, which is what makes it worth consulting when something has changed and nobody remembers changing it.
You can search it, filter by area, action or date, and Download CSV of what is on screen.
Form autosave does not fill it. The builder writes every couple of seconds, so logging each save would bury the trail under a record per keystroke — only meaningful changes, such as the public link or access settings, produce an entry.
Notifications
The bell in the top bar collects things that need your attention. They appear straight away, without refreshing the page, and stay in the list until you clear them.
| You get a notification when… | Who gets it |
|---|---|
| A new response comes in on a form | Admins, the form's creator, and the Editors of the form's team (or all Editors if the form is not in a team). Viewers are not pinged, and nobody outside a team hears about that team's forms. |
| Your export is ready to download | The person who asked for it. |
| You are added to, removed from, or given a different role on a team | You. |
| A form or app is shared with you, or that access is taken away | You. |
| Someone accepts an invitation to the organization | Admins. |
| A webhook keeps failing or is switched off | Admins. |
Multiple organizations
One account can belong to several, with a different role in each. Switch with the workspace switcher in the sidebar. Nothing is shared between them: forms, responses, records and dropdown lists all belong to exactly one organization, and the separation is enforced on every request rather than by filtering in the browser.
Narrowing access within one organization
Everything above applies organization-wide. If a program spans several states or a large team, Teams scope forms and apps to just a sub-group, Projects keep a team's work in tidy folders, and Sharing grants one person access to a single form or app on its own. Members only see the teams and projects they belong to; Admins see them all.