Control data permissions for Feishu channel users

Select “Feishu” in the “Platform” dropdown on “Channels.” Enter credentials on first activation: App ID and App Secret are required when creating a channel; Encrypt Key and Verification Token are optional. When editing credentials, the form fills in the saved configuration, required fields still cannot be blank, and saving updates the whole credential set. Click “Save” after filling it in; Feishu is enabled only after saving succeeds. Cancel keeps the previous platform.

“General configuration” has a deep reasoning switch, described as suitable for complex tasks with longer model reasoning. It is off by default, which means fast mode. Enabling it gives subsequent channel questions longer reasoning time for more reliable complex analysis. The switch saves immediately and affects subsequent questions.

The “Channel preferences” text box sets response preferences for this channel, such as giving conclusions first and answering in concise Chinese. It supports up to 1024 characters with a counter at the lower right. It saves when you leave the input, and applies to every turn of questions in this channel.

The “People permissions” section appears below only after saving the channel. Its Enable allowlist switch is at the top, with status-dependent guidance: when off, any Feishu user who can contact the bot can ask data questions; when on, only allowlisted people can access it. When off, the entire list below is grayed out and unavailable, with a message that the allowlist is disabled and everyone can access it.

Click “Add person” to open “Add person to Agent allowlist,” select a person and role, then click “Authorize.” If no role is selected, the dropdown shows “Do not select any role” and explains that the user defaults to the data Agent's access scope, including all data configured for it. After authorization, the Role column labels such entries as full access when no role is specified. If a role has required variables, the dialog requires values such as dept_id before submission.

When the allowlist is enabled, questions from identified users who have no profile or authorization are rejected and appear in the “Pending approval” tab on “People.” Each record shows an avatar, name (or user_id if unavailable), status badge, and “Feishu” label on the left, with user_id below. The three columns on the right are contact information, requested access, and latest request; the far right has “Reject” and “Create profile / Link” (or “Assign permissions” for an existing profile).

Click “Create profile / Link” to open a dialog such as “Create a profile for Zhang San.” “Feishu account information” at the top shows avatar, name, email, phone, and user_id. Below, choose “Create new person profile” (name, email, and phone are prefilled) or “Link to an existing person” (search existing profiles by name). Click “Create profile” to finish.

After profile creation, the permission assignment dialog opens with a title such as “Assign Store Operations Analyst permissions to Zhang San.” Select a role and click “Authorize,” or “Assign later” to postpone. After this step, this Feishu user's next question is allowed according to the role's rules.

• Revoke access to one Agent only: in its “Channels” → “People permissions,” click the record's delete icon on the right; the confirmation button is “Remove.”
• Remove the person entirely: person details → “Dangerous operations” → “Delete person.” Confirming clears related bindings and authorizations together; with the allowlist enabled, future questions return to “Pending approval.”