Check the account and company membership
A user account alone does not define a person's responsibilities. First check that it belongs to the right organisation and has the employee profile needed for employee functions.
Team and permissions
Site employees and office managers need different information. Invite team members to the correct company and define the projects and functions they need.
Feature scope
A user account alone does not define a person's responsibilities. First check that it belongs to the right organisation and has the employee profile needed for employee functions.
Agree which projects and areas the person needs. Have the responsible administrator configure suitable rights. Viewing and editing may require different permissions, for example in the calendar.
Open the intended areas with the person. For a missing button, check profile, company membership and permissions. Review access again when responsibilities or membership change.
Check the email address, required user places and your invitation rights.
The team member signs in with the invited address or creates an account and explicitly accepts the invitation.
Check accessible projects and features together. Adjust permissions when team responsibilities change.
An everyday example
The administrator agrees the needed projects and features, configures access and then checks available areas with the person.
Questions and answers
Available areas depend on company membership, profile and permissions. Two people may therefore see different views or buttons.
Yes. Describe your team structure and workflows during an introduction so the access you need can be discussed specifically.
Your next step
Create an account for the 14-day trial or request a personal demo. The Plans and included user places are on the pricing page.