Purpose

Allows a single individual to log in and manage their own credentialing account.

Also used to represent a specific Staff member of an Organization.

Allows a corporate entity to maintain a “root account” that “owns” its data, while allowing Staff members to log in and manage that data.

How is the Member identified?

People have a “First Name” and a “Last Name”

Organizations have a single “Member Name”

Organizations also have a “Website” field

Typical default Role

Practitioner

Provider

Can the Member have “staff” users beneath it?

No

Yes. See https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3271655425

Can the Member own Activity Definitions?

No

Yes. Providers can create Activities, and their staff members can manage those Activities.

Can the Member own Learning Plan Instances?

Yes

Yes

Staff members cannot manage the Learning Plans owned by their parent Organization. The Organization must log in as itself to act on its Learning Plans.

Can the Member be listed within a complex hierarchy of accounts?

Only at a “leaf” level; People can belong to an Organization, but a Person cannot belong to another Person.

Organizations can be placed into a hierarchy representing departments of a larger entity (e.g. the government), different regions of a large corporation, etc.

See https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/739510301

How are permissions determined?

A Person “has” all of the Permissions linked to each of their granted Roles.

TODO -