Skip to main content

Removing team members

Managing team members in Tines.

Danielle Swanser avatar
Written by Danielle Swanser
Updated yesterday

You can remove team members from a team by clicking on your team name in the top left and navigating to your settings. From here, click "Users". Click the three dots beside the name of the user you wish to delete.

Note: You cannot undo this action. The user will be deactivated immediately and enqueued for deletion.

When a user is deleted in Tines, what happens to their stories, credentials, and resources?

When a user is deleted in Tines, the Stories, credentials, and resources saved in a team will remain available.

The deleted user's drafts will be deleted. Any shared credentials in those drafts will also be deleted.

What happens to a Tines API key when the user account that created it leaves the tenant?

When a user creates a Tines API key, there are several levels of access they can set during creation:

  • Tenant owner: Access to the entire tenant

  • Team: Role-based access to a specific team on the tenant

  • Service: Access to tenant permissions

  • Personal: A key tied to your identity and permissions

Note: The level of access the user can select at the time of the API key creation also depends on the user's permissions within the tenant/team.

Let's look at an example. We have a user named Jane Tino, who, within their tenant, is a tenant owner and also a team admin of "Team Automation". This would give Jane access to all four access levels mentioned above.

Within Team Automation, Jane creates Tines API keys for each level as credentials.

  • If Jane's account is active in the tenant, all four API keys will work as intended.

  • If Jane's account exists in the tenant but is deactivated, the Personal API key will break (returns a 401 status code), while the other three will still work as expected. If Jane's account is re-activated, the Personal API key will continue working again.

  • If Jane's account is completely deleted from the tenant, the Personal API key will break (returns a 401 status code), while the other three will still work as expected.

  • If Jane is re-invited back to the tenant, the Personal API key will not work (returns a 401 status code), while the other three will still work as expected.

In summary, when a user is deactivated or removed entirely from the tenant, the only API key that stops working is their Personal API key. Even if they are re-invited to the tenant, the Personal API key from before will still not work.

Did this answer your question?