Read-only access review brief for one Okta user. It reads the user profile, group memberships, application links, and recent System Log events through recued-core.okta, then asks the AI summarizer for access posture, risky signals, and next steps. It never changes lifecycle state, changes group membership, mutates app assignments, resets credentials, or calls arbitrary Okta APIs.

How it works 20 steps

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

Process (20 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 ?

■ groups default

Apply default

■ app_links default

Apply default

■ events default

Apply default

■ 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