A Solavel account identifies the person. Organization membership, app access and the operational role then determine what that person may do in a particular business and app.
#Start from the organization
Choose the organization, then open Team or its Members action. Use the invitation workflow to add a person, select the required apps and choose the roles you are allowed to delegate. Review the invitation before sending it.
The Team view groups access by organization and app. Owners may see Full access rather than a pretend employee role. A person can be an administrator in one app and a limited operator in another.
#Example: a warehouse receiver
Invite the receiver to the correct business, grant SolaStock access, select the appropriate warehouse-scoped operational role and configure the allowed warehouses. After acceptance, the receiver should be able to open the relevant receiving workflow, but not unrelated warehouses or Finance administration.
If a receiving action is missing, inspect the app assignment, role and warehouse scope together. Adding a person to the organization alone does not create every operational grant.
#Example: HR without accounting access
Give an HR team member the intended SolaHR role and department/employee scope where supported. Add Finance access only if the person's job also requires it. The member uses the HR attendance, employee or payroll controls allowed by that role.
A limited attendance role should not be tested by handing it the owner's account. Verify the person's own application access instead.
#Example: project participation
Grant the relevant SolaProjects app role, then manage project participation in the project's Team tab. App access and project-specific actions are separate checks. A direct link to a task does not remove the need to be authorized for that project.
#Profile and navigation
Use the account menu for your profile, avatar, language and theme controls. The current apps can show the Central account avatar in their desktop and mobile account controls. Check the selected organization independently of the picture: an avatar identifies a person, not a business.
#When a role cannot be assigned
An inviter can delegate only within the permissions and scope available to that inviter. Read the message and ask the organization owner to make a change that requires a higher ceiling. Removing a person's access is not a request to delete the business's historical documents.
#Related
Team, Invitations, Application roles, Account settings, Switching apps and organizations.
#Business Solutions & Examples
Follow the complete business workflow for prerequisites, app handoffs, expected balances and common exceptions.