This page covers how people get into Ettex — single sign-on with Google, or an email code — and how you control what they can reach once they are in.

Single sign-on with Google

If Google sign-in is enabled for your Ettex instance, the sign-in screen shows “Continue with Google”. It is a standard OAuth flow: the consent screen belongs to Google, Ettex receives a signed token back and never sees the password.

  1. Open the sign-in screen and choose Continue with Google.
  2. Approve access in the Google consent screen.
  3. You are returned to Ettex already signed in — the account is created on first sign-in, so there is no separate registration step.

SAML and SCIM provisioning are not available yet. If your organisation requires them, tell us what you need through the contact page — it helps us prioritise.

Signing in with an email code

Without Google, sign-in uses a one-time code sent to your address: enter the email, receive the code, enter it. There is no password to store, forget or leak. Codes have a short cooldown, so requesting several in a row will ask you to wait a moment.

Teams and roles

A team groups the people you work with and the products they can use. The person who creates the team is its owner; everyone else is added with a role.

  1. Open Teams and create a team, or open an existing one.
  2. Invite people by email address.
  3. Give each person a role — owner, admin, editor, commenter, viewer or guest.
  4. Members appear in the team list, and pending invitations are shown separately until they are accepted.

What roles control

  • Owner — full control of the team, including billing and removing members.
  • Admin — manages members and settings, but not ownership.
  • Editor, Commenter, Viewer — the same meanings as in document sharing: change, comment, or read.
  • Guest — limited access for people outside the organisation.

Team members inherit access to the products the owner has, so you buy an app once for the team rather than per person and per tool.

Removing access

Removing someone from the team takes away the products they inherited from the owner and the team documents they could reach through it. Documents shared with them individually are separate — revoke those from the Share list of the document itself.

If a sign-in code does not arrive

  • Check the spam folder first — a one-time code is a short automated message and filters sometimes treat it as bulk.
  • Asking for several codes in a row triggers a short cooldown; wait under a minute and request once more rather than repeatedly.
  • Make sure the address is the one you actually signed up with: a code is sent to the address you type, so a typo produces a code you will never receive.

Data separation

Ettex stores data per user: signing out clears the local scope and signing in with another account opens a different one, on the same machine. That matters on shared computers — one person’s documents never appear under another person’s session.