Cove Console Access Review
Overview
Backup console access is high-value: a console user can delete devices,
change retention, or restore data to another machine. MSPs review it each
quarter, after a technician leaves, and when a client's security
questionnaire asks who can reach their backups. These tools only read. Remove
or change users in the Cove console.
Permissions
| Tool |
Conduit tier |
Cove role needed |
cove_users_list |
read |
Supporter |
cove_user_roles_list |
read |
Supporter |
cove_audit_actions_list |
admin-gated: only Conduit members with the admin tier can call it |
Administrator or SuperUser. Other roles get error 13501. |
cove_users_list returns names and email addresses of your staff and your
customers' staff. Keep the output with the people doing the review.
If the user is not a Conduit admin, or the connected API user is a
Supporter, do the user and role review and say plainly that the audit log
part needs both a Conduit admin and an Administrator API user.
Anti-triggers
- Device backup status: use
cove-backup-health.
- Customer states, products or storage: use
cove-customer-inventory.
Workflows
Quarterly access review
cove_auth_context_get for the root PartnerId.
cove_partners_list with fetch_recursively: true and fields: [0, 1]
to get every customer ID and name.
cove_users_list with partner_ids: the root plus the customers to
review, at most 100 IDs per call. Split larger trees into batches.
cove_user_roles_list to name the roles.
- Flag, in this order:
- SuperUser accounts. There should be very few; each needs an owner
who can justify it.
- API users with Administrator or SuperUser. The connector itself
needs only Supporter unless someone uses the audit log.
- Users at the root customer who are not on the current staff list the
reviewer gives you.
- Users at an end customer whose email domain is not the MSP's or that
customer's.
- Shared or generic logins (
admin, backup, support).
- Report one row per user: customer, login, name, email, role, and the flag
that applies. Users with no flag go in a count, not the table.
Technician offboarding check
- Run steps 1 to 4 above for the whole tree.
- Find every account that matches the leaver's name or email, at every
customer level. MSP staff often have logins at several end customers.
- If the audit log is available, call
cove_audit_actions_list for the
last 30 days with user_id set to each matching account, to see what
they did before leaving.
- List the accounts to remove. Removal happens in the console.
Who changed or deleted something (admin-gated)
cove_audit_actions_list needs from and to as Unix seconds. Narrow it:
| Argument |
Use |
partner_id |
Actions performed in this customer |
entity_partner_id |
Actions on things owned by this customer |
include_all_sub_partners |
Include every sub-customer |
user_id |
Actions by one console user |
entity |
e.g. Account (device), AccountProfile, Partner, User, Product |
operation |
e.g. Remove, Delete, Modify, Add, PasswordReset |
result |
Succeeded or Restricted |
count_limit |
1 to 1000, default 100 |
reverse_order |
true for newest first |
Common questions:
- Who removed a device?
entity: "Account", operation: "Remove", over
the window the device disappeared in.
- Who changed retention or a profile?
entity: "AccountProfile" or
entity: "Product", operation: "Modify".
- Failed attempts?
result: "Restricted" shows actions Cove refused.
If the result reaches count_limit, there may be more. Split the window in
half and query each part instead of reporting a partial list as complete.
Gotchas
- Error 13501 on
cove_audit_actions_list means the API user's Cove role is
below Administrator. A Conduit permission denial is a different message and
means the Conduit member is below the admin tier. Tell the user which one
happened.
- Cove adds a suffix to API user login names, so they look different from
the name typed when they were created.
- Passwords are never returned; password fields come back redacted.
cove_user_roles_list takes an optional partner_id; whether Cove uses it
is unconfirmed, so do not rely on it to show per-customer roles.
1---2name: cove-console-access-review3description: >4 Reviewing who can sign in to the Cove Management Console for each customer5 and with which role, spotting leavers and over-privileged accounts, and6 reading the user-action audit log (cove_audit_actions_list, admin-gated in7 Conduit and needing an Administrator API user in Cove) to see who changed8 devices, retention, users or customers.9when_to_use: >-10 When someone runs a quarterly access review of the backup console, offboards11 a technician, or needs to know who changed or deleted something in Cove.12 Use when: cove users, cove access review, cove roles, backup console13 access, cove audit log, who deleted backup, who changed retention,14 technician offboarding, or cove superuser.15metadata:16 source: https://skillmd.com/skills/wyre-ai/cove-console-access-review17---1819# Cove Console Access Review2021## Overview2223Backup console access is high-value: a console user can delete devices,24change retention, or restore data to another machine. MSPs review it each25quarter, after a technician leaves, and when a client's security26questionnaire asks who can reach their backups. These tools only read. Remove27or change users in the Cove console.2829## Permissions3031| Tool | Conduit tier | Cove role needed |32|------|--------------|------------------|33| `cove_users_list` | read | Supporter |34| `cove_user_roles_list` | read | Supporter |35| `cove_audit_actions_list` | **admin-gated**: only Conduit members with the admin tier can call it | Administrator or SuperUser. Other roles get error 13501. |3637`cove_users_list` returns names and email addresses of your staff and your38customers' staff. Keep the output with the people doing the review.3940If the user is not a Conduit admin, or the connected API user is a41Supporter, do the user and role review and say plainly that the audit log42part needs both a Conduit admin and an Administrator API user.4344## Anti-triggers4546- **Device backup status**: use `cove-backup-health`.47- **Customer states, products or storage**: use `cove-customer-inventory`.4849## Workflows5051### Quarterly access review52531. `cove_auth_context_get` for the root `PartnerId`.542. `cove_partners_list` with `fetch_recursively: true` and `fields: [0, 1]`55 to get every customer ID and name.563. `cove_users_list` with `partner_ids`: the root plus the customers to57 review, at most 100 IDs per call. Split larger trees into batches.584. `cove_user_roles_list` to name the roles.595. Flag, in this order:60 - **SuperUser** accounts. There should be very few; each needs an owner61 who can justify it.62 - **API users** with Administrator or SuperUser. The connector itself63 needs only Supporter unless someone uses the audit log.64 - Users at the root customer who are not on the current staff list the65 reviewer gives you.66 - Users at an end customer whose email domain is not the MSP's or that67 customer's.68 - Shared or generic logins (`admin`, `backup`, `support`).696. Report one row per user: customer, login, name, email, role, and the flag70 that applies. Users with no flag go in a count, not the table.7172### Technician offboarding check73741. Run steps 1 to 4 above for the whole tree.752. Find every account that matches the leaver's name or email, at every76 customer level. MSP staff often have logins at several end customers.773. If the audit log is available, call `cove_audit_actions_list` for the78 last 30 days with `user_id` set to each matching account, to see what79 they did before leaving.804. List the accounts to remove. Removal happens in the console.8182### Who changed or deleted something (admin-gated)8384`cove_audit_actions_list` needs `from` and `to` as Unix seconds. Narrow it:8586| Argument | Use |87|----------|-----|88| `partner_id` | Actions performed in this customer |89| `entity_partner_id` | Actions on things owned by this customer |90| `include_all_sub_partners` | Include every sub-customer |91| `user_id` | Actions by one console user |92| `entity` | e.g. `Account` (device), `AccountProfile`, `Partner`, `User`, `Product` |93| `operation` | e.g. `Remove`, `Delete`, `Modify`, `Add`, `PasswordReset` |94| `result` | `Succeeded` or `Restricted` |95| `count_limit` | 1 to 1000, default 100 |96| `reverse_order` | `true` for newest first |9798Common questions:99100- **Who removed a device?** `entity: "Account"`, `operation: "Remove"`, over101 the window the device disappeared in.102- **Who changed retention or a profile?** `entity: "AccountProfile"` or103 `entity: "Product"`, `operation: "Modify"`.104- **Failed attempts?** `result: "Restricted"` shows actions Cove refused.105106If the result reaches `count_limit`, there may be more. Split the window in107half and query each part instead of reporting a partial list as complete.108109## Gotchas110111- Error 13501 on `cove_audit_actions_list` means the API user's Cove role is112 below Administrator. A Conduit permission denial is a different message and113 means the Conduit member is below the admin tier. Tell the user which one114 happened.115- Cove adds a suffix to API user login names, so they look different from116 the name typed when they were created.117- Passwords are never returned; password fields come back redacted.118- `cove_user_roles_list` takes an optional `partner_id`; whether Cove uses it119 is unconfirmed, so do not rely on it to show per-customer roles.