What Is OBAC in Hoicko?

OBAC is an access-control approach used to manage who can access business information in Hoicko. It helps organizations structure access around their operational requirements instead of giving every user unrestricted access.

Introduction

As organizations grow, managing access manually becomes increasingly difficult.

A workspace may contain hundreds of users, multiple departments, different projects, and sensitive information.

Without a structured access model, users may receive more access than they actually require.

OBAC helps organizations approach access management in a more structured way.

How Access Control Works Conceptually

Think of access management as three layers:

User → Role/Responsibility → Information Access

For example:

Employee → Sales Team → Sales Information

or:

Manager → Project Manager → Project Management Information

This approach creates a relationship between what a person does and what they need to access.

Why OBAC Is Useful

A structured access model can help:

• Organize permissions
• Reduce unnecessary access
• Support departmental separation
• Improve administrative control
• Make permission reviews easier
• Support secure collaboration

Example

Suppose an organization has:

• HR
• Finance
• Sales
• Operations

Instead of giving every employee broad access, administrators can structure access based on responsibilities.

The HR team can work with HR processes, while finance users can access relevant financial workflows.

This creates a more controlled workspace without preventing departments from collaborating where required.

Common Mistakes

Avoid:

• Giving everyone administrator access
• Creating unnecessarily broad permissions
• Forgetting to update access after role changes
• Keeping access active after employees leave
• Giving temporary access without reviewing it later

FAQ

Q. What is OBAC used for?
OBAC is used to structure and control access to business information.

Q. Does access control prevent collaboration?
No. Proper access control allows collaboration while limiting unnecessary access.

Q. Should permissions be reviewed regularly?
Yes. Permissions should be reviewed when roles, responsibilities, teams, or projects change.