Skip to main content

​
Organizations

An organization is your top-level workspace. Everything you do in TextSetu happens inside one.

​
Creating an organization

If you have no organization yet, the onboarding screen prompts you to create one. You can also create additional organizations later from the Organizations area. Provide a name; a URL slug is generated automatically. The creator becomes the Owner.

​
Switching organizations

If you belong to more than one, use the org switcher in the top navigation to move between them. Your current organization scopes everything you see — projects, members, glossaries, and so on.

​
Organization settings

Owners and admins can manage organization settings, including:
  • Name and logo — the logo appears in the org switcher and settings.
  • Enabled features — Translation Memory and Glossary (both on by default for new orgs). Turning one off permanently deletes all of that feature’s data across the org, so it runs a danger-style confirmation — you type the org name to confirm, just like deleting the org.
  • Custom languages — define languages beyond the built-in list (owner only); they appear in every language picker. Custom languages share one standard icon.
  • Members and roles — see Roles & Permissions.
  • Danger zone — deleting the organization (Owner only).

​
Inviting members

From the organization’s Access page, invite people by email and choose the role(s) they should have. They receive an invitation email.
  • A new user is prompted to create an account (set a password) when accepting.
  • An existing user just clicks Accept — in the email or from the Pending Invitations banner shown at the top of the app.
Accepting an organization invitation activates all prepared access at once, including any project and team memberships staged for that person. See the invitation flow below for the details.

​
Teams

A team is a named group of people inside an organization (for example, a “Localization Team” or “Marketing Team”). Teams make access management scale: add people to a team once, then assign the team wherever it’s needed.

​
Creating a team

From the Teams area, create a team and give it a name. Add members and give each a team role (Team Admin or Team Member).

​
Assigning a team

A team can be assigned to:
  • A project — every team member gets access to that project.
  • The organization — grants org-level access to the whole team.
This is the recommended way to onboard a group of translators: build the team once, then assign it to each project they work on. When you later add someone to the team, they inherit all of the team’s assignments automatically.

​
Team vs. direct membership

You can grant access either way:
  • Direct membership — add a person individually to a project. Best for one-offs and project leads.
  • Team assignment — add a person to a team, then assign the team. Best for groups who work on the same set of projects.
Both can apply at once; a person’s effective access is the combination of all their roles from every source.

​
How invitations cascade

When you invite someone and also stage project/team access for them:
  1. Invite creates an invitation tied to the organization and sends an email.
  2. If the person isn’t active in the org yet, their project/team memberships are created as pending.
  3. When they accept the org invitation, all those pending memberships are activated at once.
  4. If the person is already active in the org, any new project/team access you give them is active immediately — no second acceptance needed.
This means you can fully prepare a new translator’s access up front, and a single “Accept” turns everything on.
Related: Roles & Permissions · Projects