Skip to main content
Sani’s available work depends on two separate controls: whether Sani is hired and what Sani currently has permission to access.

​
Hiring controls capability

An unhired Sani cannot run product actions. Sani may describe the permission-aware capabilities that hiring would unlock, but no callable actions are available until Sani is hired. Hiring and firing Sani affects paid capability and subscription state. It does not create or remove Sani’s permanent workspace identity.

​
Permissions control access

Discovering an available action does not grant Sani authority to run it. Sanilog checks the current workspace, Sani’s hired state, and Sani’s permissions again when an action runs. Changing Sani’s access changes what Sani can do. If a request is outside that access, ask the company Owner or an authorized Manager to review Sani’s permissions rather than broadening another team member’s access.
Last modified on August 8, 2026