Things you should know

Resources and lifecycle states appear throughout setup. These distinctions explain how Owlie represents access and uses employment data.

A resource is the offering, not someone's access

A resource describes what your organization offers and how it is requested and fulfilled. An assigned resource is that offering assigned to one identity. Ten people receiving the same resource have separate assignments, each with its own state.

For connected systems, an assignment can link to an account. Owlie calls entitlements within that system Grants. Examples include group membership and folder permissions. An account and its Grants are related, but they are not the same thing.

See The Owlie model for examples of identities, assignments, and Grants.

Normalize lifecycle before building lifecycle policies

Your sources may describe people as active, hired, terminated, or on leave. Owlie maps source fields into identity attributes, then uses lifecycle rules to turn those inputs into a normalized lifecycle state. Policies can use that state without having to understand each source's vocabulary.

Decide when future hires should receive access and what people on leave should retain. Configure a fallback for missing or unfamiliar source values.

Lifecycle state is also distinct from whether someone can sign in to Owlie. In particular, entering TERMINATED disables their Owlie account; changing away from it does not automatically re-enable that account. Downstream access changes depend on configured policies and fulfillment.

Read Lifecycle state and overrides before importing your population and configuring joiner, mover, and leaver policies.

Next, set up your organization.