aevatar-lark-provisioning

Lark bot resource provisioning automates granting full access to private documents, folders, and sheets created by a bot. It uses Lark APIs to assign permissions for specific users after resources are generated.

If personal user ID resolution fails during access granting, Lark provisioning falls back to sharing the resource organization-wide. This ensures the document or sheet remains accessible without requiring manual ID correction.

Yes, you need an active Lark bot with API access to set up document access permissions. The bot executes the API calls required to assign personal access rights or trigger the org-wide fallback.

Yes, you can use Lark APIs to share private bot sheets organization-wide. When individual user access cannot be resolved, the provisioning script automatically broadens the sheet's permission scope to the entire org.

Lark bots require explicit API access and valid user ID resolution to share newly created folders. If the target user cannot be resolved, the bot must default to org-wide sharing to grant access.

The best way to manage Aevatar agent access to private Lark sheets is automating permission assignment via Lark APIs. This handles personal access granting directly and defaults to org-wide access when user IDs are unresolvable.