Capabilities
Additional functionality:
The Sigma Computing connector supports automatic account provisioning and deprovisioning.
Connector actions
Connector actions are custom capabilities that extend C1 automations with app-specific operations.
The
user_id value is the account’s Sigma member ID (memberId), which the connector also uses as the account’s ID.
Notes:
- Team Admin access is sync-only. You can review Team Admin access in C1, but the connector does not grant or revoke it. A Team Admin already belongs to the team and needs no Team Member grant, so granting Team Member access to a member who is already a Team Admin of that team fails with an error that names the member as a Team Admin. To change a member’s Team Admin status, update it in Sigma.
- The connector syncs your organization’s Sigma account types, including any custom account type you created, and shows each account type name exactly as Sigma stores it. Each account type offers Assigned access that your users can request and that C1 can provision.
- A Sigma member holds one account type at a time, so account types are mutually exclusive: granting one replaces the account type the member currently holds. Granting the account type the member already holds changes nothing.
- Sigma has no unassigned state for account types, so C1 cannot revoke a member’s current account type. To change a member’s access, grant the replacement account type instead. Revoking an account type the member no longer holds succeeds without any change.
- New accounts default to the account type value
viewwhen Account Type is empty. Account type grants do not change that default. - The account creation form retains User Kind and Send Invitation for compatibility, but changing these fields has no effect. Sigma’s defaults apply, including sending an invitation email to non-embed users.
- Sigma has no hard delete. Deleting an account deactivates the Sigma member and reassigns its documents to the credential owner. Account sync includes deactivated members and shows them as disabled.
- Sigma doesn’t document that reactivating a member gives back the documents it reassigned at deactivation. Expect them to stay with the new owner unless they are moved back.
- Provisioning an account for an email that belongs to a deactivated member reactivates that member instead of creating a new one. The member keeps its account type unless the account creation form sets Account Type.
- A deactivated account stays in C1 as disabled after sync. To restore access, run Enable User on the account. The member keeps its account type, so grant a different account type only if it needs one. Granting an account type to a deactivated member does not reactivate it.
- If Sigma reports that an email is already in use but the connector cannot match it to exactly one member, account provisioning fails with an error instead of waiting. Check that member in Sigma and then retry the request.
- The Enable User and Disable User actions reactivate and deactivate a member. Members deactivated through SCIM can only be reactivated in your identity provider, so enabling them fails. Sigma advises against deactivating SCIM-provisioned members through its API, so deactivate those in your identity provider too.
- Revoke Team Member access before deleting or deactivating an account because Sigma does not allow team membership changes for inactive members.
- Granting Team Member to a deactivated member who is not already in the team fails with an error that says how to reactivate it. The grant does not reactivate the member.
Gather Sigma Computing credentials
Create API client credentials
1
Sign in to your Sigma organization.
2
Select your user avatar and then select Administration.
3
In the side panel, select Developer access. From the displayed API base URL, copy only the host, without
https:// or a path (for example, aws-api.sigmacomputing.com).4
Click Create new to open the Create client credentials dialog.
5
For Select scopes, select REST API.
6
Select a credential owner with the Admin account type and permission to read and manage members, teams, and team membership, and then click Create.
7
Copy and securely store the Client ID and Client Secret. Sigma does not display the secret again after you close the dialog.
Configure the Sigma Computing connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Sigma Computing connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Sigma Computing and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
In the Settings area, click Edit.
8
Enter the required configuration:
- Domain (required): Domain of your Sigma instance (e.g. aws-api.sigmacomputing.com) See: https://help.sigmacomputing.com/reference/get-started-sigma-api#identify-your-api-request-url
- Client ID (required): Client ID for your Sigma Computing instance
- Client Secret (required): Client Secret for your Sigma Computing instance
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. View the logs to confirm that information is syncing.