ArdSaor

ArdSaor Atlassian app

AI Clearance for Jira

Track AI requests, active grants, expiry reviews, and evidence in JSM.

Track AI requests, active grants, expiry reviews, and evidence in Jira Service Management. Built for admins who need a focused Jira workflow rather than another broad platform.

Try on Atlassian Marketplace Read documentation

Trials, purchase, and exact pricing are handled on Atlassian Marketplace.

Forge-builtBaseline app runtime and storage use Atlassian Forge. Data handling documentedPrivacy and retention details are published for admins. Support targetsSupport response windows and SLA terms are visible before rollout.

Product summary

AI Clearance is for AI-heavy teams and regulated or sensitive-data organizations already using Jira Service Management as an internal request layer. Admins approve tools into a requestable catalog; employees request one user access grant for one approved AI tool, purpose, and duration; reviewers decide, track expiry, and preserve evidence.

Best for: AI-heavy teams, security teams, IT owners, and regulated or sensitive-data organizations that already use JSM as an internal request layer.

Not for: Runtime AI control, prompt monitoring, provider app/license/role assignment, or a replacement for IAM/IGA.

Where it fits

Use AI Clearance when ai tool access lifecycle is creating repeated admin work or weak evidence. Start from the Marketplace listing, then use the docs for rollout details.

Product view

AI Clearance Marketplace image showing AI access lifecycle intake inside Jira Service Management.
AI access lifecycle inside JSM: AI Clearance Marketplace image showing a Jira Service Management request form for AI tool access, requested duration, and lifecycle evidence.

Use cases

  • Replace spreadsheet or custom Assets-based AI access approval tracking with Jira records.
  • Give employees a clear request path for approved AI tools and timeboxed access.
  • Block duplicate pending or active requests for the same tool.
  • Apply access duration and review-before-expiry controls.
  • Keep AI access evidence ready for security, compliance, or management review.

Core capabilities

  • Requestable AI tool catalog approved by admins before employees can request access.
  • One-user, one-tool access requests with stated purpose, duration, duplicate-request blocking, and approve or deny records.
  • Active grant records, expiry reviews, governance logs, and evidence exports without maintaining a custom JSM Assets schema and automation stack.
  • Optional Okta or Microsoft Entra configured-group membership actions when connected mode is configured.
  • Supported tools and models catalog with risk defaults for governance templates.

Typical workflow

  1. Curate the catalog

    Admins approve AI tools into a requestable catalog with risk levels, defaults, and optional connector bindings.

  2. Collect requests in JSM

    Employees request individual access to one approved AI tool for a stated purpose and duration.

  3. Review and decide

    Reviewers approve or deny the request, apply duration, and record rationale.

  4. Fulfill and evidence

    Connectorless approvals are fulfilled manually; connected tools can add, remove, or check the approved user in the configured Okta or Entra group and retain evidence.

  5. Review lifecycle

    Expiry, review-before-expiry follow-up, escalation, and retention sweeps keep the access record current.

Security, privacy, and support

  • Baseline app state is stored in Atlassian Forge storage.
  • Connected mode is optional and requires explicit admin configuration.
  • Connector credentials are stored through Forge secret storage.
  • Connector-mode Forge Remote requests to ArdSaor Core are scoped to connector testing, tenant binding, identity matching, and configured-group add, remove, or check actions.
  • IdP and app admins remain responsible for making the configured group control the real app, license, role, or resource.
  • Admins can review privacy, security, SLA, and support documentation before rollout.

Operational links

FAQ

What problem does AI Clearance solve?

AI Clearance creates a Jira-native lifecycle record for one user requesting timeboxed access to one approved AI tool for a stated purpose. It is meant to avoid ad hoc approvals in chat, email, spreadsheets, or custom JSM Assets builds.

Does AI Clearance change group membership automatically?

Only within the configured-group boundary. When Okta or Microsoft Entra connected mode is configured, AI Clearance can add, remove, or check the approved user in the configured group. IdP or app admins must make that group control the real app, license, role, or resource.

Does it monitor what users type into AI tools?

No. The product governs access requests, decisions, grants, expiry, and evidence. It does not inspect prompts, prove runtime AI usage, or replace IAM/IGA.

Where is app data stored?

Baseline app data is stored in Atlassian Forge storage. Optional connector operations use ArdSaor Core only when connected mode is explicitly configured.

Related ArdSaor apps and solutions

Access Evidence screenshot from the Atlassian Marketplace listing showing access review findings, reviewer decisions, and evidence pack workflows.

Access reviews and audit evidence

Access Evidence

Run Jira access reviews with remediation tracking and auditor-ready evidence packs.

Works with
Jira Cloud; review workflows can include Jira projects and Confluence spaces as documented
Status
Available on Atlassian Marketplace for Jira Cloud
Product page Docs Marketplace
DriftGuard screenshot from the Atlassian Marketplace listing showing Jira board and filter drift monitoring.

Jira configuration drift

DriftGuard

Catch risky Jira board and saved-filter changes before teams lose trust.

Works with
Jira Cloud; board monitoring requires Jira Software
Status
Available on Atlassian Marketplace for Jira Cloud
Product page Docs Marketplace

Solution

AI Access Governance for Jira

AI-heavy teams and regulated or sensitive-data organizations often already use Jira Service Management as the internal request layer. AI Clearance adds the missing access lifecycle: admins approve AI tools into a requestable catalog, employees request one user access grant for one approved tool, and reviewers track purpose, duration, expiry, fulfillment, and evidence.

AI Clearance Access Evidence

Explore this solution

Solution

Audit Evidence for Jira and Confluence Controls

Audit evidence is easier to trust when it comes from the workflow where the decision happened. ArdSaor apps preserve access review decisions, remediation status, AI access approvals, drift history, and supportable exports in Jira-native workflows.

Access Evidence AI Clearance DriftGuard

Explore this solution