Compliance command
Overview
This is the set of commands which we use related to sharing with user
Compliance Report
The compliance-report command allows administrators to generate compliance reports from the command line just as they would in the Keeper Admin Console. It provides visibility into record permissions by node, user, and record title, supports filtering by owned or shared records, and enables exporting the results to a file for auditing, analysis, or record-keeping purposes.
Power Commander
Command: Get-KeeperComplianceReport
-Format
table (default), json, or csv.
-Output
File path for json or csv. Not used for table.
-Username
Limit to records owned by listed enterprise email(s). Repeatable.
-Node
Limit to owners under the given enterprise node (and descendants, per resolution logic).
-JobTitle
Limit to owners whose job title matches (repeatable).
-Record
Filter by record UID or title pattern (wildcard). Repeatable.
-Team
Limit to records owned by members of the given team(s). Repeatable.
-Url
Keep records whose Login URL contains the given substring(s). Repeatable.
-Shared
Only shared records.
-DeletedItems
Only records in trash. Cannot be combined with -ActiveItems.
-ActiveItems
Only active (not in trash) records. Cannot be combined with -DeletedItems.
-Rebuild
Rebuild the in-session compliance cache from Keeper.
-NoRebuild
Use existing in-session cache when valid; build once if missing.
-NoCache
After the report, clear the in-session compliance cache.
-Aging
Add aging columns from audit data: Created, Last Password Change, Last Modified, Last Rotation (extra API work; uses a separate aging cache with a one-day TTL per record).
Example:
Python CLI
Command: compliance report
Flags:
--format : Format of output {table,csv,json}.
--output : Output path to resulting output file (ignored for "table" format).
--rebuild, -r : rebuild local data from source.
--no-rebuild, -nr : prevent remote data fetching if local cache present.
--no-cache, -nc : remove any local non-memory storage of data after report is generated.
--node : Node ID or name of node (defaults to root node).
--regex : Allow use of regular expressions in search criteria.
--username, -u : Username user(s) whose records are to be included in report.
--job-title, -jt : JOB_TITLE job title(s) of users whose records are to be included in report.
--team : Team name or UID of team(s) whose members' records are to be included in report.
--record : Record UID or title of record(s) to include in report.
--url URL : URL of record(s) to include in report.
--shared : Show shared records only.
--deleted-items : Show deleted records only.
--active-items : Show active records only.
Example:
Compliance Team Report
Shared folders can be shared with both Keeper Teams and individual users. The compliance report provides visibility into shared folder access, allowing administrators to view the permissions and access levels that each team has to these shared folders.
Power Commander
Command: Get-KeeperComplianceTeamReport
Parameters
-Format
table (default), json, csv.
-Output
Path for json / csv (ignored for table).
-Node
Limit to owners under this enterprise node (and descendants per internal resolution).
-Team
Filter by team name or UID (repeatable).
-ShowTeamUsers
Add team_users: member emails for each team (comma-separated in table).
-Rebuild
Rebuild compliance cache.
-NoRebuild
Use cache when valid.
-NoCache
Clear compliance cache after completion.
Example:
Python CLI
Command: compliance team-report
Flags:
--format : Format of output {table,csv,json}.
--output : Output path to resulting output file (ignored for "table" format).
--rebuild, -r : Rebuild local data from source.
--no-rebuild, -nr : Prevent remote data fetching if local cache present.
--no-cache, -nc : Remove any local non-memory storage of data after report is generated.
--node : Node ID or name of node (defaults to root node).
--regex : Allow use of regular expressions in search criteria.
--show-team-users, -tu : show all members of each team.
Example:
Compliance Record Access Report
The compliance record-access report provides a list of all records that have either (a) been accessed by or (b) are currently accessible to specified user(s). The report also includes relevant event details such as the application used, IP address, timestamp, and other associated access information for auditing and compliance purposes.
Power Commander
Command: Get-KeeperComplianceRecordAccessReport
Parameters
-Email
Users to report on: enterprise email(s), numeric enterprise user ID(s), and @all. Repeat -Email for multiple values. If omitted, behaves as @all.
Example -Email user1, user2...
-ReportType
history: audit-driven record access. vault: all vault records per user from the compliance snapshot, with audit fields when available.
-Format
table, json, or csv.
-Output
File path for json or csv export.
-Node
Optional. With Username / Team, limits which enterprise users are in scope (same semantics as other compliance reports).
-Username
Optional. Filter to specific enterprise user email(s).
-Team
Optional. Filter to members of the given team(s) (name or UID).
-Pattern
Optional. Wildcard filters (-like on each column). Cannot be used with PatternRegex (different parameter sets).
-PatternRegex
Optional. Regex filters on the tab‑joined row. Cannot be used with Pattern. example "login"
-Rebuild
Rebuild the in-session compliance snapshot cache from the server.
-NoRebuild
Prefer using an existing in-session cache when possible.
-NoCache
Clear the in-session compliance cache after the command finishes.
-Aging
Add aging columns: created, last_pw_change, last_modified, last_rotation.
Example:
Python CLI
Command: compliance record-access-report
Flags:
--format : Format of output {table,csv,json}.
--output : Output path to resulting output file (ignored for "table" format).
--rebuild, -r : Rebuild local data from source.
--no-rebuild, -nr : Prevent remote data fetching if local cache present.
--no-cache, -nc : Remove any local non-memory storage of data after report is generated.
--node : Node ID or name of node (defaults to root node).
--regex : Allow use of regular expressions in search criteria.
--username, -u : Username user(s) whose records are to be included in report.
--email, -e : Email username(s) or ID(s), use "@all" for all users.
--report-type : Type of record-access data: "history" or "vault" {history,vault}.
--aging : Include record-aging data.
Example:
Compliance Summary Report
The compliance summary report displays aggregated information about records within the enterprise, grouped by record owner by default. Support for grouping by additional entities may be added in future enhancements to this feature.
Power Commander
Command: Get-KeeperComplianceSummaryReport
Parameters
-Format
table, json, csv.
-Output
File path for json / csv.
-Node
Filter with node.
-Team
Limit to members of listed team(s).
-Rebuild / -NoRebuild / -NoCache
Same cache semantics as other compliance reports.
Example:
Python CLI
Command: compliance summary-report
Flags:
--format : Format of output {table,csv,json}.
--output : Output path to resulting output file (ignored for "table" format).
--rebuild, -r : Rebuild local data from source.
--no-rebuild, -nr : Prevent remote data fetching if local cache present.
--no-cache, -nc : Remove any local non-memory storage of data after report is generated.
--node : Node ID or name of node (defaults to root node).
--regex : Allow use of regular expressions in search criteria.
Example:
Compliance Shared Folder Report
Similar to the compliance team-report command, this command generates a report detailing the access that all entities—both teams and individual users—have to all shared folders across the enterprise.
Power Commander
Command: Get-KeeperComplianceSharedFolderReport
Parameters
-Format
table, json, csv.
-Output
Output file for json / csv.
-Node
Limit owner scope for snapshot fetch.
-Team
Filter which folders appear: folder must match user and/or team filters (same pattern as team report).
-ShowTeamUsers (-tu)
Include team members in the email column as (TU)email.
-Rebuild / -NoRebuild / -NoCache
Cache control.
Example:
Python CLI
Command: compliance shared-folder-report
Flags:
--format : Format of output {table,csv,json}.
--output : Output path to resulting output file (ignored for "table" format).
--rebuild, -r : Rebuild local data from source.
--no-rebuild, -nr : Prevent remote data fetching if local cache present.
--no-cache, -nc : Remove any local non-memory storage of data after report is generated.
--node : Node ID or name of node (defaults to root node).
--regex : Allow use of regular expressions in search criteria.
--show-team-users, -tu : Show all members of each team.
Example:
Last updated
Was this helpful?

