Manage your team and permissions

Access in Evergrowth is organized around teams and users. A team is a named role that carries its own permissions; a user is a person you invite and assign to a team, so they inherit exactly what that team allows. You manage both from Settings, under Users management, which is available to people whose team can manage users or teams. For what each team can do, see Teams, roles, and permissions.

Before you start

You need a team that can open Settings and manage users or teams. If you do not see Settings in the left navigation, or the Users management card, ask a teammate who has that access to make the change.
Have the email addresses of the people you want to invite ready. Each person is invited by email.
Decide which team each person should be on. Every workspace ships with four ready-made teams - Admin, Sales Ops, Sales Rep, and Read-only - and you can also create your own.

Open Users management

In the left navigation, open Settings, then choose the Users management card.
The screen has two tabs:
- Teams - the teams in your workspace and the permissions each one grants.
- Users - the people in your workspace and the team each one is on.

Manage users

Open the Users tab. It lists everyone in your workspace in a table with columns for Email, Name, Role (the team they are on), Status, Credit limits, Ownership rules, Created (how long ago the person was added), and Last active (how long ago they last did something in the workspace). Use the Search box to find a person by name or email.

Both dates read as an age rather than a calendar date - “3 days ago” - with the exact date on hover, because the question these columns answer is who has gone quiet, not what the date was. Last active is empty for somebody who has never used the workspace, which is the state worth spotting: an invitation accepted and then never used looks exactly like a licence nobody needed.

Sort by clicking Name, Created, or Last active. The list opens sorted by Last active, most recent first, so the people who are actually using their access sit at the top and the dormant ones fall to the bottom. Reverse it and you have your adoption follow-up list in one glance - the teammates who joined weeks ago and have not come back, which is where onboarding help or a reclaimed seat usually belongs.

Last active records work the person did themselves, so it stays an honest read on real usage rather than on anyone acting on their behalf.

Invite a user

Select Invite new at the top right. The Invite users window opens.
In the Enter emails box, type or paste one or more email addresses. Valid addresses appear as removable chips under Emails to add; click a chip to remove it.
Choose the Team the invited people should join. The team carries their permissions.
Optionally set Credit limits for the people you are inviting: a Weekly amount, a Monthly amount, or both. Leave an amount empty (it shows No limit) for no cap on that period. The same amounts apply to every address in this invitation. See Set credit limits below.
Select Save to send the invitations, or Close to cancel. Each person receives an email with a link to set their password and join.
If any address could not be invited, the window switches to Failed invitations and lists each failed Email with the Reason. The addresses that succeeded are still invited.

Edit a user’s name or team

In the person’s row, select the edit (pencil) button. The Edit “[email]” details window opens.
Change the Name if needed.
Choose a different Team to change what the person can do.
Set or change this person’s Credit limits - a Weekly amount, a Monthly amount, or neither. Clearing an amount removes that cap.
Select Save to apply, or Close to discard.

Remove or restore access

To remove access, select the remove (Delete user) button in the person’s row. A Remove Access? prompt asks you to confirm; select Remove. The person’s Status changes to Deactivated and they can no longer sign in.
To restore access, select the Grant access button in a deactivated person’s row and confirm at the Grant access? prompt. Their status returns to Active.

You cannot remove access from the last remaining admin, so the workspace can never lock itself out.

Reset a user’s password

When someone is locked out and the self-service reset email is not reaching them, you can generate a reset link and pass it on yourself.

In the person’s row on the Users tab, select the Reset password button (the padlock icon). The same action sits on a team’s page next to each of its members, and inside the person’s Edit window.
The Reset password window asks you to confirm for that email address, and states that no email is sent - you share the link yourself.
Select Generate link. The window then shows the link with a copy button beside it.
Copy it and send it to that person directly. Opening it takes them to the screen where they set a new password.
Select Done to close the window.

The link is valid for 7 days, and generating a new one invalidates that person’s older links. You never see or set the password yourself.

Two things worth holding to. A live reset link is as good as access to that account until it is used, so send it to the person one-to-one rather than posting it in a shared channel. And when the person can still receive their email, point them at Forgot password? on the login screen instead - self-service leaves you out of the loop entirely. That works for a teammate who was invited but never signed in, too, so a lost invitation email does not need a reset link from you.

Manage teams

Open the Teams tab to see each team as a card, with a System label on the four ready-made teams, the team’s description, its Credits limits, its member count, and how many ownership rules point at it. From a card’s menu you can Edit the team, Assign users, or Delete it (System teams cannot be deleted). Open a card to see the team’s people and to invite or assign more.

Create a team

Select Create team. The Create team window opens with two ways to start:
- From scratch - give the team a Name and Description, then set its Permissions on the matrix below.
- From template - give the team a Name and pick a Template to copy a ready-made team’s permissions as a starting point.
Select Create.

Set permissions on the matrix

The permission matrix is a table with a Feature column and two checkboxes per row, View and Manage:

View lets the team see that area and its data.
Manage lets the team create, change, and run things in that area. Turning on Manage turns on View automatically.
Sub-areas sit indented under their parent and need at least View on the parent before they can be enabled. Hover a locked checkbox to see which parent it needs.
A dash in place of a checkbox means that column does not apply to that row - a heading that only unlocks the features beneath it has no Manage, and an action with nothing to look at has no View. There is nothing to fix; the matrix is only asking you about the choices that change something.
Hover a row’s name for a one-line description of what its View and its Manage let the team do, so you are granting a capability rather than guessing from the label.

The areas are grouped as Agent training center, Agents, Automations, Accounts & contacts, Reports, Integrations, Settings, and Widgets. For the full list of areas and what each ready-made team starts with, see Teams, roles, and permissions.

Edit or delete a team

Edit opens Edit team: [name], where you change the Name, Description, Credit limits, and Permissions. (For a System team you can still adjust the permissions and name.)
Delete opens Delete team: [name]?. If the team still has people on it, you must pick another team to Move users to before deleting; an empty team is removed outright.

Assign users to a team

From a team’s Assign users option (or the Assign existing button on its page) you can:

Add users - search for people and add them to this team, which gives them its permissions.
Move out - move selected people from this team to another team. To empty a team you must move its people somewhere, so create another team first if none exists.

Set credit limits

A credit limit caps how much of the shared credit pool one person, or one team, can spend in a week or in a month. Nobody is capped until you cap them, and you can cap a person, a team, or both. For what limits are for and what happens when one is reached, see Credits and billing.

Setting a limit needs the same access as managing the thing you are limiting: managing Users for a person’s limit, managing Teams for a team’s limit.

On one person or one team

The Credit limits field appears in three places, and works the same way in all of them: the Invite users window, a person’s Edit window, and a team’s Edit window. It offers two amounts:

Weekly - how many credits this person or team may spend in a week.
Monthly - how many credits they may spend in a month.

Leave an amount empty for no cap on that period; the empty field reads No limit. Set both to keep a month’s budget from being spent in its first days. A weekly amount higher than the monthly one is rejected with “Weekly limit cannot be higher than the monthly limit”, since it could never bind. Clearing an amount that was set removes that cap.

On many people or teams at once

Both tabs carry a Bulk update credit limits action at the top right, for setting the same limits across a group rather than opening each record.

Select Bulk update credit limits on the Users tab (for people) or the Teams tab (for teams). The Bulk update credit limits window opens.
Enter the Weekly and Monthly amounts you want to apply. The note reads: “An empty amount is left untouched, or removes that limit when overriding.”
Under Apply to, choose All users (or All teams) or Specific users (Specific teams). Choosing the specific option adds a searchable multi-select to pick exactly who.
Decide on Override existing limits. With the switch off, anyone who already has a limit for that period keeps theirs and only the rest get the new one - the safe way to set a floor across a growing team without undoing individual arrangements. With it on, your amounts replace what is there, and an empty amount removes that limit rather than leaving it alone.
Select Apply. A confirmation summarises what actually changed, for example how many were set, updated, removed, or kept their existing limit. People who have never signed in are reported as skipped, because a cap needs somebody to attach to.

Where limits show up

On the Users tab, the Credit limits column shows a small bar per capped period with credits left against the limit; No limits where none is set.
On a team card and at the top of a team’s own page, a Credits block shows the same, with the period named and No credit limits where none is set.
Everyone sees their own position in the credits control in the top header bar: sections for Your limit, Team limit, and Workspace limit, each with credits left, credits used, and when that window reopens. The pill itself shows whichever of the three runs out first, since that is the one that will actually stop their work.

See which rules route work to a person or team

Both the Users list and the team cards show how many ownership rules assign records to that person or team, counted separately for accounts and contacts. A dash means none do. If you can open the Ownership rules page, the count is a link straight to it.

Read this before you deactivate somebody or empty a team: a rule whose assignees are all inactive stops routing and is flagged as needing attention, so the records it used to cover quietly stop being assigned to anyone.

Evergrowth admin

The invite and edit windows also show an Evergrowth admin switch, with the note “Bypasses every permission check.” This is reserved for Evergrowth staff: it overrides the team permissions entirely, can only be granted to an evergrowth.io address, and only appears for someone who already has it. People with it show a red Evergrowth Admin label on the Users list. It is not one of the teams you assign.

What happens next

New invitations appear on the Users tab with the status Invited. Once the person follows the email link and sets their password, their status becomes Active.
Changes to a person’s name or team, and changes to a team’s permissions, take effect for that person’s next actions. Moving someone to a different team changes what they can see and do.
Removing access sets the status to Deactivated straight away; restoring it returns the person to Active.
A credit limit takes effect for that person’s or team’s next runs. Raising or removing a limit clears a block that had stopped their work, so a paused run can be resumed - see A run stopped because a credit limit was reached.
A generated reset link changes nothing on its own. The password only changes once the person opens the link and sets a new one, and the link stops working after 7 days or as soon as a newer one is generated for them.

Eva: credit limits are set on the same three windows that create and edit people and teams (invite a user, edit a user, edit a team) and in bulk from a Bulk update credit limits action on each tab - there is no separate limits screen. Two amounts per subject, Weekly and Monthly, either of which may be left empty for no cap. In bulk, the Override existing limits switch is the fact people miss: off means already-capped subjects are left alone, on means an empty amount deletes that cap. Users who have never signed in cannot be capped and are reported as skipped.

Eva: “Users management” lives under Settings and has two tabs, Teams and Users. A “Team” is the role - it carries the permission set, and each user is assigned to exactly one team; there is no separate “Roles” screen. The four ready-made teams are Admin, Sales Ops, Sales Rep, and Read-only, but a company can rename them, re-permission them, or add custom teams, so do not treat the names as fixed. “Evergrowth admin” is a staff-only override, not an assignable team. The earlier model of four fixed roles (Admin, Salespeople, Read-only, Evergrowth admin) has been replaced by this teams-and-permissions model; map any older role wording onto the current teams.

Teams, roles, and permissions
Credits and billing - what credits are, and what limits are for
A run stopped because a credit limit was reached
Roles: who does what
Sign in
Navigate the workspace
Why a navigation item is missing