Permissions and Data Access

Leina can use supported actions through connected Apps. What it can read or change depends on the connector’s available actions, the connected account’s permissions, and team settings.

Check the connection

Open Connections and use the account intended for the task. Review the requested access during authorization. Connecting one account does not imply access to every workspace, folder, channel, or record in that service.

Adding Leina to team chat and authorizing a business App are separate steps. If a task needs CRM records or documents, connect the service that owns those records.

Set connection permissions in Console

The steps below use the current Notion connection screen checked on October 7, 2026. Labels are shown in Chinese as they appear in that interface; available controls can differ by connector.

1. Open 应用连接 (Connections), find the App, and open its management page. Verify the connected account and status first.
2. Find 连接权限 (Connection Permissions). Review 团队默认 (Team Default): members not assigned to a custom permission group use this setting.
3. To define a different scope, choose 添加权限组 (Add Permission Group). Use 分配成员 (Assign Members) to select the intended members.
4. Under 接口调用范围 (Action Scope), review the available read, write, and high-risk actions. 自定义限制 (Custom Restrictions) allows only selected actions and disables Proxy and call_tool; 无限制 (Unrestricted) allows all of them.
5. Save only after reviewing the members and operations. Verify the resulting access as an intended member with non-sensitive test records.

A permission group is an access configuration, not automatically a Slack channel or WeCom chat group. Choosing read actions also does not establish a document- or row-level filter. Check which records the source account can reach, and apply any supported data restrictions separately.

Before sharing a result, check its destination and participants. Permission to read an internal record does not by itself authorize posting its contents to an external group. See the member and group planning example.

Define the task’s scope

For a read-only task, specify the source, date range, fields, and expected output. Ask for source links or record references so you can check the result.

For changes, also specify the destination and affected records. Ask Leina to prepare a draft when you want to review the proposed changes first. Before requesting publication, sending, or deletion, check the recipients, content, and scope.

Do not paste account passwords or raw access tokens into a task message. Use the connection flow for account authorization.

When access is incomplete

Check whether the correct account is connected, whether it has access to the relevant records, and whether the App supports the required action. A supported App does not imply that every feature of that service is available through Leina.

For help, provide the App name and a description of the failure to support. Avoid including passwords, tokens, or unrelated private records. See the privacy policy for the published privacy terms.