← ZillizCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Zilliz
Snapshot Sep 30, 2026 · 23:15 UTC · version 1.4.4
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user wants to manage database users, roles, passwords, or access privileges in Milvus.",
"included_files": [],
"name": "user-role",
"skill_md_contents": "---\nname: user-role\ndescription: Use when the user wants to manage database users, roles, passwords, or access privileges in Milvus.\n---\n\n## Prerequisites\n\n1. CLI installed, logged in, and cluster context set (see setup skill).\n\n## Commands Reference\n\n### Users\n\n#### Create a User\n\n```bash\nzilliz user create --user <username> --password <password>\n```\n\n*Create a new database user.*\n\n#### List Users\n\n```bash\nzilliz user list\n```\n\n*List all database users.*\n\n#### Describe a User\n\n```bash\nzilliz user describe --user <username>\n```\n\n*Get details of a user.*\n\n#### Drop a User\n\n```bash\nzilliz user drop --user <username-to-drop>\n```\n\n*Drop a database user.*\n\n#### Update Password\n\n```bash\nzilliz user update-password \\\n --user <username> \\\n --password <current-password> \\\n --new-password <new-password>\n```\n\n*Update user password.*\n\n#### Grant a Role to a User\n\n```bash\nzilliz user grant-role --user <username> --role <role-name-to-grant>\n```\n\n*Grant a role to a user.*\n\n#### Revoke a Role from a User\n\n```bash\nzilliz user revoke-role --user <username> --role <role-name-to-revoke>\n```\n\n*Revoke a role from a user.*\n\n### Roles\n\n#### Create a Role\n\n```bash\nzilliz role create --role <role-name>\n```\n\n*Create a new role.*\n\n#### List Roles\n\n```bash\nzilliz role list\n```\n\n*List all roles.*\n\n#### Describe a Role\n\n```bash\nzilliz role describe --role <role-name>\n```\n\n*Get details and privileges of a role.*\n\n#### Drop a Role\n\n```bash\nzilliz role drop --role <role-name-to-drop>\n```\n\n*Drop a role.*\n\n#### Grant a Privilege\n\n```bash\nzilliz role grant-privilege \\\n --role <role-name> \\\n --object-type <Global|Collection|Database> \\\n --object-name <object-name> \\\n --privilege <privilege-name>\n# Optional: --database <database-name>\n```\n\n*Grant a privilege to a role.*\n\n#### Revoke a Privilege\n\n```bash\nzilliz role revoke-privilege \\\n --role <role-name> \\\n --object-type <Global|Collection|Database> \\\n --object-name <object-name> \\\n --privilege <privilege-name>\n# Optional: --database <database-name>\n```\n\n*Revoke a privilege from a role.*\n\n## Common Privileges\n\nCommon privileges by object type:\n\n- **Collection**: `Search`, `Query`, `Insert`, `Delete`, `CreateIndex`, `DropCollection`\n- **Global**: `CreateCollection`, `All`\n- **Database**: `ListCollections`\n\n## Guidance\n\n- Never ask the user to paste a password or API key into the conversation. Present password-bearing commands with placeholders and instruct the user to run them in their own terminal.\n- User and role management is only available on **Dedicated** clusters.\n- Built-in roles: `admin` (full access), `public` (no privileges by default -- must be granted explicitly).\n- When setting up RBAC, suggest a workflow: create role, grant privileges, create user, assign role.\n- Before dropping a user or role, confirm with the user.\n- Use `*` as object-name to grant privilege on all objects of that type.\n"
}SHA-256 of public snapshot: cc681e198b4ef3a65fe8bcef5f144a7159b269142f024798dd1d9c3ffe3a209e