Every credit operation happens inside a company, and the company is what defines the boundary of access: the data, processes, and clients belonging to one organization never mix with those of another. Within that boundary, however, not everyone needs to see or do the same things. That is where roles come in — profiles such as Sales, Credit Analyst, or Manager — which group, under a single named set, the permissions that make sense for whoever performs that function. Instead of configuring access person by person, the company defines the role once and assigns it to as many users as needed, and each user automatically inherits everything the role authorizes.This separation between person and role is what sustains governance over the credit process. A frontline salesperson does not need — and should not have — visibility into an analyst's internal approval criteria, just as an analyst has no use for the sales team's prospecting tools. By restricting each role to exactly what its function requires, the company protects sensitive client information, reduces the risk of decisions being made by people without the authority to make them, and makes it clear at any moment who can approve, reject, or change the course of a credit operation.This structure also simplifies administrative life. When a role needs an adjustment — for instance, granting visibility into a new type of report — the change is made once, on the role itself, and propagates immediately to every user who carries it, with no need to touch individual accounts one by one. The same applies to the team's lifecycle: hiring someone only requires assigning the matching role for that person to start working with the correct level of access; letting someone go, and removing their roles, immediately ends their visibility into the company's data. Companies & Roles is, therefore, the foundation that ensures team growth and operational complexity are never accompanied by a loss of control over who sees and decides what.Simplified example#
Under the hood, a role is represented by a simple data structure. An illustrative example:{
"name": "Sales",
"description": "Sales team",
"permissions": []
}
Modificado em 2026-07-28 20:38:32
