Deciding who can do what

Permissions decide which options each person sees and what they can do in them. They are handed out by role —a named set of permissions— and fine-tuned person by person. This page walks through the whole process, from giving someone new access to checking what they end up seeing.
Where do I start with a new person?
By letting them in. You do it from the Users screen and there are three ways: add them with Add employee, send them an invitation with Invite with a role, or give them the company’s shared link. In all three you choose **which role they sign in with** at that same moment. Which one to use in each case, and how to remove access when someone leaves: give a new person access.
What is a role and how do I create one?
A role is a named set of permissions —Warehouse, Sales, Administrator— that you assign to people instead of going option by option. How to create one and how to adjust what it allows: create a role.
Working by roles is what keeps the set-up manageable: when the rules for a job change, you change the role once and not person by person.
How do I change what a particular person can do?
Each person starts from their main role. On top of it you can add additional roles —for someone who does two jobs— or adjust individual options with an own setting: change a person’s permissions.
That page also explains what wins when two things say the opposite, which is the most common question: across several roles the highest access level always wins, and the own setting overrides what the roles say, both to open and to close.
How do I check what another person sees?
Without signing in with their account or asking for their password. The program lets you preview the ERP with another person’s permissions, which is how you check a change before accepting it: view the ERP as another person.
It is the step worth taking every time after changing a role. What looks obvious in the permissions tree isn’t always what shows up in the menu.
What if someone says they can’t find an option?
It is almost always their role’s permission, but not always: there are four different reasons and each one is fixed in a different place. They are set out, with what you see in each case, in why can’t I see an option in the program.
Two of them aren’t fixed with permissions, which is why it is worth ruling them out early: the module hasn’t been purchased for the installation —a ceiling that no permission opens— or the person has hidden it from their own menu.
How do I organise people into departments and work groups?
With departments (where each person works, one each) and groups (people from several departments who work together). They are not permissions: they are used for the chat, for assigning tasks and for the CRM filter. How to create and assign them: departments and groups (in Spanish).
What does closing a permission really do?
Closing an option doesn’t just hide it from the menu. The screen is no longer shown even if you reach it through a link or by typing the address: instead you get the message that there is no access to that section. The same applies to whatever the assistant can do on that person’s behalf, which never reaches beyond their permissions.
There is a deliberate limit the other way: for whoever administers the ERP, no own setting cuts back their access. That is what stops a company from being left with nobody able to get back into the permissions screen.