# Enterprise integration login

Configure enterprise identity login and manage the members allowed to sign in.

使用指南 · 模块: organization · 管理人员 · 部署形态：资料未说明 · 已确认产品版本：资料未说明 · 来源：现有文档

WeCom and WPS let employees enter AskTable from enterprise applications, reducing repeated sign-ins. Integrations belong to organizations, with each organization storing its own enterprise credentials independently. Both Cloud and private deployments support them, managed by an organization Owner or Admin.

## Configure the enterprise application

Select a platform from **Profile → Organization → Enterprise integrations** and follow its guide to create the application, configure visibility, and connect it:

**[Connect WeCom](https://docs.asktable.com/en/integrations/wecom)**

Prepare CorpID, AgentID, and Secret, and configure the application homepage and authorization domain.

**[Connect WPS Collaboration](https://docs.asktable.com/en/integrations/wps)**

Prepare AppID and AppKey, and configure permissions, visibility, and the callback URL.

A secret is required for the first connection. It is not displayed after saving; leaving it blank when editing keeps the existing secret. CorpID or AppID cannot be changed directly after saving. Disconnect before connecting to a different enterprise.

## Use the login URL provided on the page

After connecting, copy the complete callback URL from the details page and register it in the enterprise application's administration console. It can also serve as the member login entry:

- Private deployment URLs look like `/login/sso/wecom` or `/login/sso/wps` and automatically bind to the single organization.
- Cloud URLs include `?org_id=...` to specify the organization. Do not remove or change this parameter.

These URLs are not invitation links. The first enterprise login does not automatically create an account or join an organization; members must be imported first.

## Select members to import

Click **Import members** and select from the members currently visible to the enterprise application:

1. Search by name or external UID, and filter by “Importable,” “Imported,” or “Disabled.”
2. Select the people to add. Imported and disabled members cannot be selected.
3. Check the current limit, remaining slots, and slots used by this selection, then submit.

Visibility, member status, and capacity are checked again on submission. If a change to any condition causes failure, nothing in the batch is written. Refresh the candidates and select again.

Import only adds identities and organization memberships: new members become Members; an existing identity from the same enterprise reuses its account, and existing active members and roles remain unchanged. Import does not restore disabled members, nor does removing someone from the upstream address book automatically disable their AskTable membership.

Only imported people whose account and organization membership are both active can sign in through that organization's enterprise login entry. After importing, assign project roles as described in [Invite members](https://docs.asktable.com/en/organization/invitations), and configure [Data permissions](https://docs.asktable.com/en/permissions).

## Disconnect

Disconnecting deletes the current organization's integration configuration and stops logins through this enterprise application for that organization. Existing accounts, external identity bindings, memberships, projects, and historical content remain. Reconnecting the same enterprise can reuse existing identities.

Users with only WeCom/WPS credentials and no email credentials cannot create organizations or become an organization Owner.

For deployment-level Google, GitHub, WeChat, email login, and SMTP, see [Deployment authentication configuration](https://docs.asktable.com/en/deploy/authentication). These settings are not managed on the organization enterprise integrations page.