Identity of the workspace. Shown to people you invite and on exported reports.
These languages apply to content, automations, and reports — survey wording, message templates and generated report text. They do not change the language of this administration interface.
How people get into this organisation, and how they prove who they are.
In the legacy application neither settings tab has a Save button — every control, including Enforce SSO and Allow organisation join requests, appears to persist the moment it is touched, with no confirmation and no way back. This page adds an explicit Save, a dirty state, Discard changes, an unsaved-changes guard when you leave the tab, and a confirmation on Enforce SSO that names the members it would lock out.
Legacy exposes three role names but was never exercised with a lower-privileged account, so the capability lines below are invented, not observed. They are stated here because a role vocabulary that means nothing is worse than one that is wrong out loud.
| User | Role | Status | SSO | Sending | Actions |
|---|
| User | Requested | Status | Actions |
|---|
Legacy's queue reads “1 request pending” above a single row that is already Approved, with an empty user cell and no approve or reject control anywhere — while the organisation policy that feeds the queue is Disabled. Here the pending count counts rows that are actually pending, pending rows carry working Approve and Reject, decided rows show who decided and when, and the tab says so when the policy has closed the queue.
Feedback requests are sent from a connected mailbox, not from a Foxie address.
Used as the From name in emails. Use [signature] in templates to
include your signature. If unset, it is left blank.
Hi Sophie,
We would value ten minutes of your view on how the collaboration has gone this half-year. The survey is five questions.
This is legacy's actual shape, not an omission in the prototype. Sending identity in Foxie is exactly “the connected Gmail account, plus a display name”. Everything below is absent from the product — there is no screen for it and no stored state behind it.
The connection registry. Connecting opens the provider's own consent screen.
| Provider | Owner | Scope | Last refreshed | Actions |
|---|
Applies to your own account only.
Linking an identity lets you sign in with it. The same linkage appears as the SSO column on the Users tab.
The complete list is two topics. This is the only notification surface in the whole application.
Organisation-level data that leaves Foxie.
Legacy keeps every uploaded CSV file indefinitely — the raw upload, contact rows and all, sits in storage forever with no screen that lists it and no way to delete it. There is no retention control anywhere in the product; this one is invented so the question is at least asked.