Console overview

The Acrity Console is the administrative area you use to configure workspaces, connect repositories, define review policies, manage credentials, track billing, and view operational audit. This page is the general map. Specific pages explain each area in detail.

​

Who uses the Console

Roles are fixed capability sets defined by Acrity. They are not configured per organization, so the same role grants the same access in every workspace.

​

Console navigation

The left navigation lists the areas you can open in the selected workspace. Repositories, Policy Engine, Webhooks, API Keys, Audit Trail, Credentials, and Connectors require a Workspace admin. Platform admins also have access to these areas.

​

Adjacent destinations

Two related areas are reached from outside the left navigation:

​

The Overview dashboard

Overview is the first screen you see for a workspace. It orients you and surfaces the next action.

​

First-time setup checklist

For a new workspace, the dashboard shows a setup checklist that walks you through the minimum needed to receive reviews: Each item links to the area where you complete it, and the checklist marks steps as done as you progress.

​

Quick actions

Quick actions are shortcuts to the tasks you run most often, such as connecting a repository, inviting a member, opening the Policy Engine, or jumping to Billing. They target the same areas as the left navigation, so you never have to hunt for the starting point.

​

Status tiles

Status tiles summarize the workspace at a glance and highlight anything that needs attention, including:

• connected repositories and how many are ready for review;
• Connected Apps, credentials, and connectors, with any that need reauthorization or revalidation;
• recent review activity;
• billing state, including trial, wallet balance, and spend cap.

Select a tile to open the matching area.

​

Inbound webhook and review triggers

The dashboard shows an inbound webhook card with the endpoint URL and a signing secret. This is how your Git provider tells Acrity that a pull or merge request needs a review.

• When you use a Connected App, this webhook is registered for you.
• When you use a manual credential or a local connector, copy the URL and signing secret into your provider’s webhook settings.

When a matching event arrives, Acrity verifies the signature with the signing secret and starts a review. The change is processed transiently; for large changes it may be cached at rest for a limited period with automatic expiry (up to 24 hours).

​

Explore the Console

​

Recommended setup flow

​

Attention indicators

The Console highlights menus with alerts when there are pending actions, such as:

• credentials that are invalid, pending, or need validation;
• repositories not yet ready for review;
• Connected Apps that require reauthorization;
• connectors that are offline or whose last revalidation failed;
• suspended billing, an ended trial, insufficient wallet, or a reached spend cap.

When you see an alert, open the indicated menu and follow the on-screen messages. They prioritize the nearest action to restore operation.

​

Where to configure each area

​

Security and data handling

Console screens show only what is needed to administer Acrity. Sensitive data, credentials, tokens, and keys follow the policies described in Data handling and Credentials and tokens.