Managing who can see what
As a team grows, controlling who has access to which campaigns, leads, and settings becomes important. Here's how that works.
Individual accounts, not shared logins
New accounts are created with email and password, or by signing in with Google, LinkedIn, or GitHub, with email verification for accounts created directly. Team members are invited individually rather than sharing a single login.
Why individual accounts matter
When each team member has their own account, actions are tied to a specific person, which keeps accountability clear as a team grows past a handful of people. Audit logging of sensitive actions is partially implemented today and is being expanded.
Scoping access as a team grows
For teams with specific requirements around scoping access to particular campaigns or client accounts, reach out to our team to discuss what's available for your plan.
Frequently asked
Yes, each team member gets their own account rather than sharing credentials, which keeps a clear record of who did what.
More security topics
This page describes, plainly, what data moves through Dialbotix, where it goes, and what protections are actually in place today, rather than a generic security statement.
Running a call involves more than one system working together. Here are the specific named services involved, and what each one is responsible for.
Retention isn't the same for every type of data in the platform. Here's specifically what's kept, for how long, and what deleting something actually does.
Have a specific access control requirement?
Talk to our team about your setup.
