Freshness Check Permissions¶

This page covers the team permissions required to view, create, edit, archive, and delete a Freshness check on a source datastore. For the full reference of user roles, see User Roles. For the canonical matrix of every team-permission-gated action, see Team Permissions Overview.

Permission Matrix¶

The table below shows which team permissions can perform each action on a datastore the user has access to:

Key Details¶

• Viewing is available to all team permissions, including Reporter and Viewer.
• Draft work is available from the Drafter permission upward: creating a check as Draft, editing it while it stays Draft, and restoring an archived check as Draft.
• Validating a check requires the Author permission. A Drafter does not see the Validate button and saves work as a Draft without validating it.
• Anything that puts a check into evaluation requires at least the Author permission: creating or activating an Active check, editing an Active check, archiving, restoring as Active, and deleting permanently.
• Editing the Maximum Age from the Observability chart (the Edit Maximum Age button) requires the Author permission. See Edit Maximum Age.
• The same rules apply through the API. The API page lists the permission each endpoint requires.
• Admins bypass team permissions and can manage checks on every datastore in the workspace. Managers do not bypass team permissions: like Members, they need the required permission in at least one team assigned to the datastore.

See Also¶