Less dependence on one account
People can work through their own staff access rather than using the owner's credentials. That makes day-to-day responsibilities clearer and reduces the practical problems created by a shared login.
Customer management · Team & permissions
Add staff and define what they can do in SAYLS. Roles and permissions help you share customer work without giving every colleague the same access to contacts, campaigns, settings and administration.
7-day platform trial · No credit card required
The task behind the feature
Not every team member needs every setting or action.
A growing business needs more than a shared password. Sales staff, support agents and the person managing configuration do not always need the same tools. Role-based access gives you a more deliberate way to set responsibilities, while individual staff records make the workspace easier to organise as people join or leave the team.
See how the pieces fitOne practical way to use it
List the work each team member actually needs to perform. Keep customer service, campaign management and administrative settings separate where your process requires it, rather than starting with full access for everyone.
Configure the supported capabilities for a role, then assign it to the relevant staff member. Review inherited permissions and any individual changes so you understand the access the person will actually receive.
Check roles when someone changes duties or leaves the business. Test an ordinary staff account, not only the owner account, so the team can complete its work without unnecessary privileges.
Check inherited permissions as well as the actions enabled for an individual staff member.
Why this is useful in practice
People can work through their own staff access rather than using the owner's credentials. That makes day-to-day responsibilities clearer and reduces the practical problems created by a shared login.
Give people the capabilities they need for customer work while restricting unrelated configuration. A smaller, purposeful set of tools is often easier for a new team member to learn.
Reuse appropriate roles as you add colleagues instead of rebuilding access decisions every time. Review the current plan's staff allowance and expand capacity when the business genuinely needs more people.
Choose a useful starting point
Your first useful workflow
Assign a role with the capabilities the person needs. Start with one support role with reviewed capabilities and review the result before choosing a plan.
Understand the setup, the costs and the next step before you decide.
No. Permissions control access to supported actions, but people still need to understand customer privacy, messaging rules and your internal process. Combine suitable access with clear instructions for daily work.
Inherited access comes from the selected role. Change the role or its capabilities when you need to remove inherited permission; review the effective access rather than assuming an individual checkbox overrides everything.
Staff capacity depends on the current plan. Use the live comparison to choose the appropriate team allowance, and ask about a custom enterprise setup if your staffing requirements do not fit the published packages.