Managing Roles and Permissions in Hoicko

What are roles and permissions?

Roles and permissions determine what users can access and which actions they are allowed to perform within the Hoicko environment.

Why are permissions important?

Without appropriate permissions, users may:

• See information they do not need
• Modify important records
• Change workflows
• Access administrative settings

Use role-based access

Instead of managing every user independently, organizations can establish access patterns based on responsibilities.

For example:

Team Member

May need to:

• View assigned work
• Update tasks
• Collaborate

Manager

May additionally need:

• Approval access
• Broader project visibility
• Team oversight

Administrator

May require:

• User administration
• Workspace configuration
• Workflow management

Least privilege principle

The safest approach is:

Give users the access they need to perform their work, without granting unnecessary privileges.

Review permissions regularly

Permissions should be reviewed after:

• Role changes
• Department transfers
• Promotions
• Project changes
• Organizational restructuring

FAQs

What are Hoicko permissions?
Permissions determine what users can access and what actions they can perform.

Why should permissions be limited?
Limiting unnecessary access reduces the risk of accidental or unauthorized changes.

Should managers and team members have identical access?
Not necessarily. Access should reflect responsibilities.

When should permissions be reviewed?
They should be reviewed when responsibilities change and periodically as part of access governance.

What is least-privilege access?
It means providing only the permissions necessary for a user to perform their assigned responsibilities.