Methods, API keys, connections and credits belong to an organization, not a person. Switch between yours, or create one, in the workspace menu at the top of Studio's sidebar. A new organization starts on the Free plan. Free's monthly credits and builds go only to an eligible new user's first organization.
Roles
- Owner: everything an Administrator can, plus transferring ownership and deleting the organization. An organization has exactly one Owner, who must transfer ownership before leaving.
- Administrator: everything a Member can, plus API keys, billing, members, security, the name and the logo.
- Member: builds, runs and changes methods and workflows, and connects website accounts. It is the default role for invitations and for people who join through single sign-on.
- Reader: views methods, workflows, builds and usage, but cannot run or change anything.
Members
Under Settings, Members, owners and administrators:
- invite by email as a Member (the default), an Administrator or a Reader (invitations expire after 48 hours; inviting the same address again replaces the invitation with a new link, role and 48 hours). Members and open invitations take your plan's seats: 1 on Free, 3 on Starter, 10 on Pro, unlimited on Business and Enterprise; an invitation past them returns
403 seat_limit, and a bigger plan in Billing adds seats; - change roles;
- remove members, who lose access immediately.
Members leave from their own entry in the list. Settings also changes the name and logo.
Single sign-on
Enterprise, and Business with the single sign-on add-on (added in one click under Billing), can connect a SAML or OpenID Connect identity provider under Settings, Security. It applies only to the organization's verified domains. An owner or administrator sets it up in four steps:
- Verify a domain. Choose Add domain and enter the part after the @ in your team's addresses. At your DNS provider, add the TXT record Studio shows (name
_fous-verification.<domain>, valuefous-verification=<token>), then choose Verify domain. Fous reads public DNS, so a new record can take a few minutes to be visible; until then Studio says the record isn't visible yet. A domain can be verified by one organization only. - Connect the identity provider. For SAML (Okta, Microsoft Entra, Google Workspace and others), create a SAML app with the single sign-on URL (ACS) and entity ID Studio shows, or import its metadata URL; send the person's email as the NameID or an email attribute and sign the assertions. Then paste or upload the app's metadata XML, which must include an HTTP-Redirect sign-in address. For OpenID Connect, create a web app with the authorization code flow, the scopes
openid email profileand the redirect URI Studio shows, then enter its issuer URL, client ID and client secret. The secret is stored encrypted and only its last 4 characters are shown. - Test sign-in. Signs in once through the provider without changing who is signed in to Fous, and shows the result under Security, with the reason when it fails.
- Require single sign-on (optional). Available once a domain is verified and a test has worked.
People who sign in through it get an account if they have none and join as Members, unless you choose another role under New members join as (an open invitation's role wins). The provider speaks only for verified domains: it cannot sign in an address on any other domain.
With Require single sign-on on, people on those domains can sign in only through it: email codes, Google and Microsoft send them to single sign-on instead, members already signed in another way are signed out, and accounts on those domains keep their address (a person cannot move onto one with an emailed code, and a member cannot change theirs away from one). Connecting a different provider turns the requirement off until it is tested again; removing the provider, or the last verified domain, ends it.
Transfer ownership
The Owner can transfer the organization to an Administrator or a Member: open the person under Settings, Members and choose Transfer ownership. It takes effect immediately and the previous Owner becomes an Administrator. A Reader must be made a Member first.
Delete an organization
Only the Owner can delete an organization, with Delete organization under Settings, after typing the organization's name to confirm. Any unpaid invoice is settled first: if it cannot be, the deletion stops and nothing changes. An Enterprise agreement in force has to be ended first; write to hello@fous.com.
Deleting stops workflows, API keys and the subscription immediately. After that, only the Owner can open the organization. Its data is permanently erased after a 14-day recovery window, during which the Owner can restore it from Studio.
Restoring brings back its methods, connected accounts, API keys, members and any credits it has left; workflows return to the on or off state they had. A canceled subscription does not come back: the organization returns on Free. Its schedules run again, and its webhook triggers work once you choose a plan.