managing-users SKILL.md skillA
managing-users from celigo/ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add celigo/ai/managing-users@git:20261017.e0e159fPins git:20261017.e0e159f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- celigo/ai
- Path
skills/managing-users/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.e0e159f, committed Oct 17, 2026
- First version recorded
- May 20, 2026
- Size
- 14,496 bytes
- Repository stars
- 4
- License
- MIT
Manage Celigo account users -- inviting users, updating permissions, configuring access levels (administrator, manage, monitor, integration-only), enforcing MFA/SSO, and disabling accounts. Use when adding team members, changing permissions, auditing access, or managing user lifecycle.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- TIER:1 --> # Managing Users A user (internally called an "ashare") represents a **person's access grant** to a Celigo account, defining what they can see and do. Concerns when managing users: - **Access strategy** -- choosing between account-wide access (administrator, manage, monitor) and per-integration access for least-privilege control - **Integration-level permissions** -- granting manage or monitor access to specific integrations, optionally combined with account-wide monitor as a baseline - **Security enforcement** -- requiring MFA or SSO per user to meet compliance requirements - **Feature flags** -- controlling access to APIM features and whether monitor-level users can edit retry data - **Lifecycle** -- inviting, disabling, and removing users as team composition changes Users are an account administration concern, not a flow or integration resource. ## Access Strategies There are four strategies for granting access. Choose based on the principle of least privilege. ### Administrator Full account administration. Can edit all resources, manage users, and change account settings. Cannot transfer ownership or manage owner permissions. ### Manage (Account-Wide) …
Read the whole file at its exact version.
How to install
mdr add celigo/ai/managing-users@sha256:44303cea5f4a9bf8The line at the top of this page pins the label git:20261017.e0e159f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_obn46y2ipcdxlqlo)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 20, 2026 and Oct 17, 2026, about one every 50 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.e0e159f latest | 2026-10-17 | e0e159f | 14,496 B | A | view · diff |
| git:20260722.b000fd6 | 2026-07-22 | b000fd6 | 13,553 B | A | view · diff |
| git:20260618.593a4ab | 2026-06-18 | 593a4ab | 10,038 B | A | view · diff |
| git:20260520.7414ff1 | 2026-05-20 | 7414ff1 | 10,104 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14496 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
celigo/ai · 4 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_obn46y2ipcdxlqlo GET https://markdownregistry.com/api/v1/resolve?ref=celigo/ai/managing-users GET https://markdownregistry.com/api/v1/blob/44303cea5f4a9bf81b2736f62d1b4a7389c0ba8971c948420b2a7aa3648ac68b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.