Blissfully combines a wide range of access detection techniques with information about your company to find and categorize relationships employees have with apps.
To find out who's using what, Blissfully looks at data from SSO, integrations, and email parsing.
To understand why a person may or may not have access, Blissfully looks at the apps assigned to a team and the teams a person is on. It also looks at app-based roles like owner, IT admin, and billing owner. Finally, Blissfully matches app access workflows to apps and people.
Understanding the status of an employee's relationship to an app lets you spot potential security and compliance risks with ease. Blissfully has four status options:
Approved: The employee has access, as intended
Optional: The employee is allowed access, but does not need it and currently does not have it
Needs Provisioning: The employee should have access, but does not
Unintended: The employee has access, but should not
Every team has an access matrix in its Access tab. The access matrix shows all team members, all apps assigned to the team, and the status at each intersection:
Hovering over the icon at the intersection of a row and column shows the reasoning behind the status:
While most access comes from team or role assignment, some people may need access to an app for reasons not otherwise reflected in Blissfully. To keep good records and enforce process, you should use app access workflows when granting new access outside of onboarding.
Every app has its own app access workflow in Blissfully. To view, edit, or launch an app access workflow, open the app detail view and head to Workflows:
The default workflow contains just one task: provision app. If you want multiple approvals, need the recipient to complete a training, or have any other particular requirements, edit the template and add custom tasks.
Use the link below for further information on customizing workflows.