Manage Celigo account users with access levels, MFA/SSO, and lifecycle operations.
npx skills add https://github.com/celigo/ai --skill managing-users
Please help me install this Agent Skill. Skill: managing-users Source: https://github.com/celigo/ai/tree/main/skills/managing-users Command: npx skills add https://github.com/celigo/ai --skill managing-users
Manage Celigo account user access without over-permissioning, while ensuring security requirements like MFA/SSO and keeping permissions auditable over time.
Use it when onboarding team members, changing what people can do per integration, enforcing compliance controls, or troubleshooting unexpected access behavior.
Use the managing-users skill to invite a new user with monitor access for the account and manage access for a specific integration by adjusting accessLevel and integrationAccessLevel.
High-intent search queries and answers about installing and using this skill.
To manage Celigo user access, assign account-wide roles or use integrationAccessLevel for per-integration permissions. This enforces least privilege by restricting user capabilities to specific integrations rather than the entire account.
The difference between accessLevel and integrationAccessLevel is scope: accessLevel assigns account-wide roles like administrator or monitor, while integrationAccessLevel restricts permissions to specific integrations for tighter security.
Yes, you can enforce MFA and SSO for user accounts in Celigo. Administrators can mandate multi-factor authentication and single sign-on to secure user logins and meet integration security compliance requirements.
The best way to handle stale user invitations and inactive accounts is to disable users instead of deleting them. This preserves audit history while managing user slots by removing pending or inactive access securely.
You control operational capabilities like retry-data editing and APIM access by adjusting optional feature flags during user permission updates. This restricts or allows specific operational actions safely without altering base access levels.
You need a valid user email and integration IDs to update access levels because the system requires a confirmed user identity and target integration scope to safely apply permission changes and handle invitation acceptance states securely.
YOYOMAIIAutomate Clerk SDK installation, middleware configuration, and environment variable setup for web frameworks.
heaptracetechnologyHarden cloud identity controls with federated MFA across AWS, Azure, and GCP.
Mekann2904Analyze log files to extract error patterns and detect anomalies.
sitharaj88Generate least-privilege GCP IAM policies, roles, and service accounts.
