Configuration and administration
Enterprise identity login
Choose an enterprise login method, import members in advance, and assign the projects and data they can access.
Guide · Module: admin · Administrators · Deployment: Not specified · Confirmed product versions: Not specified · Source: Existing documentation
WeCom and WPS let employees sign in to AskTable with their enterprise identities. An organization administrator first connects the application and imports the members allowed to sign in, then assigns their project permissions and data scope.
Who configures it, and where
The current organization's Owner or Admin configures WeCom or WPS from Profile → Organization → Enterprise integrations. Both Cloud and private deployments are supported; each organization stores its own enterprise credentials independently.
| Login method | Configuration location | Who configures it |
|---|---|---|
| WeCom, WPS | The organization's enterprise integrations page | Organization Owner / Admin |
| Google, GitHub, WeChat, email login | Deployment environment variables | Deployment operators |
| SMTP, SMS | Deployment environment variables | Deployment operators |
Email, OAuth, and email delivery are not configured on the enterprise integrations page. See Deployment authentication configuration for variables and how changes take effect.
Connection sequence
Create an enterprise application
Create an application on the enterprise platform and configure permissions and its visibility scope. WeCom requires CorpID, AgentID, and Secret; WPS requires AppID and AppKey.
Enable the organization integration
Enter the credentials in the AskTable enterprise integration details and enable it. Saving the configuration does not automatically import members or mean that the external credentials have been verified.
Register the login URL
Copy the full callback URL shown on the page into the enterprise application's administration console. Private deployments bind to a single organization; Cloud URLs include org_id, which must be preserved in full.
Select members to import
Click Import members, search, filter, and select people within the application's visibility scope, and submit after checking the remaining capacity. New members become Members; existing roles remain unchanged, and importing again does not reactivate disabled members.
Assign project and data permissions
Add members to the projects they need, choose the project Admin or Member role, and configure Agent and data permissions for your business needs. Use a test member to verify login and query results.
For detailed steps and platform screenshots, see Connect WeCom and Connect WPS Collaboration. For import, identity scope, and disconnection rules, see Enterprise integration login.
Common issues
| Symptom | Checks and resolution |
|---|---|
| Cannot find Enterprise integrations | Check the current organization and whether your organization role is Owner or Admin; system administrator status is not the criterion |
| Cannot find a person to import | Check the enterprise application's visibility scope and address book permissions, then refresh the import candidates |
| First enterprise login fails | Confirm that the member has been imported and that the account, organization, and membership are all active; login does not create members on demand |
| A disabled person still cannot log in after being imported again | Import does not restore disabled memberships; handle this through organization member management |
| Login opens the wrong organization or reports an organization parameter error | Use the full URL copied from the page; do not remove or change org_id on Cloud |
| Login succeeds but a private project cannot be opened | Add an explicit project role first, then check data permissions |
| Login fails after a secret update | Verify the application credentials for the same enterprise; leaving the secret blank when editing keeps the old one, while a reset secret requires the new value |
| Email delivery fails | Check SMTP configuration in the deployment environment and restart the relevant processes; see Deployment authentication configuration |
Enterprise login identifies members. For messaging channels and web embedding, see Messaging channels and Web embedding, respectively.