Recued
Menu
← Back to recipes

Okta user access brief

by recued-core v1 25 views

Use “Okta user access brief” in Recued. It provides a read-only access review brief for one Okta user.

How it works 18 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (18 steps)
user_id trim
Trim whitespace from setting user id
log_filter template
Generate text from a template
user ?
groups_raw ?
app_links_raw ?
logs_raw ?
defaults defaults
Apply defaults
group_count count
Count items in groups
app_link_count count
Count items in app links
event_count count
Count items in events
summarize ?
group_rows slice
Take a subset of
app_rows slice
Take a subset of
event_rows slice
Take a subset of
group_table to_table
Format results as a data table
app_table to_table
Format results as a data table
event_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

okta setting =
focus setting = Summarize this Okta user's lifecycle state, group memberships, visible application links, recent System Log activity, access-risk signals, and concrete next steps. Do not invent facts outside the Okta data.
since setting =
until setting =
user id setting =
row limit setting = 20
max length setting = 900

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Okta connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

okta oktaidentityaccess-reviewusersgroupsapplicationssystem-logai-summarypack:okta

Details

18 steps 7 configurable settings recipe_id: user-access-brief-okta