Permissions and Governance
Give your SaaS to different companies for safe use.
From enterprises and applications to roles, projects and business interfaces, access and execution scopes are defined respectively, allowing AI to follow existing business boundaries when using capabilities.
Your product, why do you need it?
Your product, why do you need it?
After the product is launched, different enterprises, administrators, and personnel on duty require different entrances and data. Hiding the menu does not mean that the interface is secure, and the company or project specified in the conversation cannot be used as the basis for authorization.
How to access your business?
How to access your business?
The following is an illustration of the implementation path. The business interface will not be called or commands will be executed on the official website.
- 01
Confirm identity and open relationship
Determine people and businesses from login context, check application status and validity, and distrust self-declared identities in conversations.
Check the outputCurrent enterprise, application and user context - 02
Limited resources and operations
Determine accessible resources based on roles, projects, and regions, and verify the permissions required to read data and control devices respectively.
Check the outputObjects allowed to be accessed and scope of operations - 03
Perform allow and deny testing
Use actual roles to test legitimate queries, cross-enterprise reads, and unauthorized controls; unauthorized access should be stopped and the results should not be fudged by the model.
Check the outputReviewable allow and deny records
Use with other base capabilities
Use with other base capabilities
These capabilities belong to the same basic platform and can be combined according to business needs.