Every person who signs in, builds workflows, or chats is a member, and how you invite them, organize them, and grant them access is what shapes who can do what.
Members and service accounts
Tines 3B has two kinds of identity, and it helps to keep them straight.
A member is a human: someone with an email address who signs in and works in Tines 3B.
A service account is a non-human identity, meant for scripts, CI jobs, and services, and it holds its own permissions and keys rather than belonging to a person.
Both live under the same settings area, on separate tabs, but this article is about members, the human side.
The lifecycle of a member
A member moves through a few clear states:
Invited. An admin invites someone by email, and Tines 3B sends them a sign-in link. Until they first sign in, they show as invited.
Active. Once they've joined and are using Tines 3B, they're an active member. If they hold tenant-admin access, that's shown too.
Deactivated. A member who should no longer have access can be deactivated, which signs them out immediately. Their account isn't deleted, so their history stays intact.
Reactivated. A deactivated member can be brought back later, reusing the same account and email rather than starting fresh.
You can filter the members list by status and search it, so finding active people, pending invites, or deactivated accounts is straightforward.
Everyone gets a personal space
When a member joins, Tines 3B automatically gives them personal workflows of their own. It's private to them, a place to build and experiment without affecting shared work, and its access is fixed rather than something you configure. This means a new member always has somewhere to start, from the moment they sign in.
Groups keep members organized
Members rarely need access managed one by one. Groups let you gather people together, so you can grant a whole team access to a space or a connector in a single step rather than repeating yourself for each person. You can add someone to groups right when you invite them, so they arrive with the right access already in place. Managing access at the group level is the scalable way to run a growing tenant.
Learn how to create and manage your groups here.
Access is the sum of direct and inherited grants
What a member can actually do comes from two sources, added together. There are the roles granted to them directly on a space, connector, or skill, and there are the roles they inherit from the groups they belong to. A member's detail view shows both side by side, so you can see not just what they can reach but why, including which group a given piece of access comes from. When you remove someone's access, it's clear whether you're editing a direct grant or need to adjust a group.
Who manages members
Managing members, inviting, deactivating, reactivating, and changing access, is an administrative capability, reserved for people with the right tenant permission. There's one important caveat worth knowing: if your tenant syncs its users from an external identity provider, that provider owns who exists, and Tines 3B locks manual invites and deactivation so the two can't fight over the same accounts. In that setup, you manage people in your identity provider and Tines 3B follows along.
Learn how to manage your member here.