> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating and Managing Access Policies with Albus

## Overview

Albus can create, update, and manage access policies through natural language, including the AppStore setup that policies require as a prerequisite. Instead of working through a multi-step modal, describe what you need and Albus handles the steps.

What Albus can do:

* Create new access policies from a description of the apps and conditions to apply
* Read and search your existing policies
* Update or delete policies
* Add missing apps to the AppStore before creating the policy that needs them
* Flag when a matching policy already exists, and offer to update it instead

## Getting started

Access policy management is available in **Albus chat**. No additional setup is required: the policy tools are available by default to Lumos admins.

## Creating a policy

Tell Albus what you need. For example: *"Create an access policy for the Engineering team that gives them GitHub, AWS, and Linear."*

Albus will:

1. Check which apps are in your AppStore, and offer to add any that are missing
2. Verify that permissions are available for those apps
3. Check for existing policies that would conflict
4. Present a summary of the proposed policy and ask you to confirm
5. Create the policy once you confirm

You can refine the policy before confirming, and Albus updates its proposal based on your feedback.

## Updating a policy

Describe the change you want, for example: *"Add Figma to the Design team policy."* Albus finds the existing policy, shows you a preview of the change, and applies it after you confirm.

## Creating policies in bulk

For large-scale policy creation, such as building policies from an access matrix or from role-mining output, Albus works through the list iteratively. Give it the set of apps and conditions, and it reports the result for each policy: success, partial (where some apps were unavailable), or an error with an explanation.

## What Albus checks before it writes

Albus always asks for confirmation before creating, updating, or deleting a policy. Before it presents that confirmation, it:

* Validates that the required apps are in the AppStore, and adds them if they are not
* Checks that permissions are configured for those apps
* Detects conflicting policies with the same conditions
* Reports anything it could not resolve

## Limitations

* Policy tools are available in Albus chat. They are not yet available as Lumos Flow steps.
* Albus creates and manages policies on behalf of the signed-in admin, so that admin's permissions apply.
* For complex multi-team bulk creation, Albus works through policies iteratively. Review the summary it returns for each batch.

Questions? Contact your Lumos account team or open a support ticket.