Accessing User Management
Admins are able to manage and provision users within Fluint directly. Navigate to Settings → User Management. Here you'll see a full list of everyone currently licensed in your org. From there, you can:
Add new users
Delete users
Promote a user to admin access
Control whether 'welcome emails' are sent
Trigger a CRM or Call integration backfill
Edit user emails or names
Adding New Users
Click Add User and enter the new user's details.
Recommended: Check the box to send an automated welcome email first. This notifies new users automatically via email.
Click Add User to confirm.
Important: Always use the email address that connects back to your CRM. This is what Fluint uses to match the user to their deals and activity.
The "Need Sync" Alert
After adding a new user, you may see a red Need Sync indicator. This is expected - it's your cue from Fluint to backfill data for that user.
To resolve it:
Click the Backfill button for your CRM integration.
If you also have a call tool connected (e.g., Gong, Salesloft), click the Backfill button there as well.
This triggers a 30-day backfill for the new user across both services, so Olli has the deal context it needs to start working right away.
To verify it worked: Head to Pipeline View, filter by the new user, and confirm their deals are populating (you may need to give it a few minutes).
Promoting Users to Admin
If you need another team member to manage users or settings:
In User Management, check the box next to the user
Then, click the 'Promote to Admin' button at the top
Removing Users Who've Left
When someone leaves the team:
Select the user in User Management and click Delete.
Confirm the deletion in the pop-up.
Nothing is lost. Meetings, content, and Olli's work for that user all remain intact and accessible. The individual simply loses their ability to log in. Safe to do at any time.
However, please note that restoring users is not currently supported. So, be sure before deleting access. If the pause for the user is temporary, we'd recommend finding another way to limit access instead.