Skip to main content
When Lumos evaluates a Lumos Expression Language (LEL) expression, it provides a set of named objects, called the context. user is one context object. access_request is another. Which objects are present depends on where the expression runs. A provisioning workflow for an AppStore request has the request, but an onboarding workflow doesn’t. This page lists every context object, its attributes, and where you can use it. For syntax, operators, and functions, see Using the Lumos Expression Language in Workflows.

Context objects at a glance

If you reference an object that isn’t available where the expression runs, the expression fails. In a workflow, that creates an Error Task.

user

user is the identity a workflow runs for, or the identity a condition is being checked against. identity is an alias for the same object, so user.email and identity.email return the same value. The workflow builder suggests user.. Identity matching rules accept only user..

Standard attributes

Any attribute can be empty. Use or to supply a fallback, for example user.title or "Employee".

Custom attributes

Read a custom attribute by the name shown in your Lumos settings:
To use an attribute from a connected system such as Okta or Workday, first store it as a custom attribute on the identity.

Groups

user.groups is a list of the groups the user belongs to. Each group has name, external_id, and description.
Lumos loads groups only when it evaluates a condition. It loads source_app only in access policy and workflow conditions, not in branch steps, pre-approval rules, or escalation policy exclusions. In workflow step inputs and notification templates, user.groups is an empty list and user.source_app is empty.

access_request

access_request holds the AppStore request that started the workflow. Use it to pass what the requester entered into a provisioning step. For example, a step can read a GitHub username from an intake field instead of asking someone to look it up. Read an intake answer by its reference key:
Use brackets for every key. Dot notation reads the wrong value when a reference key matches a built-in name such as items or get.

Where access_request is available

  • AppStore account provisioning workflows and permission provisioning workflows, in step inputs. The answers are the same whether the request came from the Employee AppStore, Slack, or an AI assistant over MCP.
  • AppStore account deprovisioning workflows and permission deprovisioning workflows, in step inputs. Here access_request is the removal request, not the request that originally granted the access.
  • Pre-approval rules, through the condition builder. See Condition-only attributes.
access_request isn’t available in onboarding, offboarding, mover, or attribute sync workflows, or in Wait Until steps.

account

account is an app account that Lumos discovered and needs to match to an identity. It is available only on the account side of identity matching rules. In workflows, a step that targets an account uses the linked identity’s user attributes instead. For example, to match accounts that still use an old email domain:

Special values

These names are always defined in workflow step inputs. They aren’t attributes. An expression returns them to tell Lumos what to do with the field.

Condition-only attributes

The attributes below exist only in condition builders. You pick them from a menu, so you don’t type them. You also see them as paths in conditions read or written through the Lumos API.

Identity conditions

These apply to access policies, workflow conditions, branch steps, flexible approvals, escalation policy exclusions, and pre-approval rules.

Pre-approval rules

Role bulk assignment


FAQs

Can I use identity instead of user? Yes, in workflow step inputs and conditions. Both names refer to the same identity. Identity matching rules accept only user.. Why is user.groups empty in my workflow step? Lumos loads group membership only when it evaluates a condition. To act on group membership in a workflow, add a branch step with a group condition. Why can’t I reference access_request in my onboarding workflow? Onboarding workflows start from a new hire, not from an AppStore request, so there’s no request to read. access_request is available only in workflows an AppStore request starts. What happens if an intake field wasn’t answered? access_request.intake_responses["<key>"] is empty. Use or to supply a fallback, for example access_request.intake_responses["region"] or "us".

Other Questions?

Contact support@lumos.com or your CSM.