HelloID administration
Once HelloID is set up, HelloID administrators manage the available modules, assign rights and roles, monitor system activity, troubleshoot incidents, maintain integrations, and handle updates to policies, workflows, and settings as organizational needs evolve.
To get started, log in to the Admin dashboard and Navigate the HelloID Interface.
Administrator tasks
These are key responsibilities for HelloID administrators:
Monitor HelloID. HelloID includes a number of tools designed to monitor its functioning and troubleshoot issues.
Any Incidents are reported in the Incidents widget on the Admin dashboard.
For help with incidents and other common issues, see Troubleshooting.
HelloID will send notifications about incidents and events in modules, as configured. Make sure notifications are sent to all persons who need to be involved. See Quick Reference: portal and user configuration.
Pages in the Admin and Provisioning dashboards (see Navigate the HelloID Interface) provide immediate insight into user activity and actions performed by HelloID and their results.
HelloID's audit logs store long-term records of activity in your HelloID portal.
Audit logs provide detailed information about a wide range of events and activities in your HelloID environment, ranging from user actions to system events and incidents. By analyzing these logs, administrators can monitor and review system activity, troubleshoot issues, and maintain an overview of what happens in the environment.
For troubleshooting purposes, Explore available audit log data.
Keep HelloID up to date. Since HelloID runs in the cloud, you don't need to do any technical maintenance on it. However, your HelloID environment is tailored to your organization. As your organization evolves, changes in people, processes, and systems can all affect your HelloID setup. Staying alert to these changes helps you maintain security, compliance, and smooth daily operations.
It is recommended to periodically scan the organization for new requirements and changes that impact HelloID. Ideally, this should be carried out by an identity and access management committee that includes representatives from all stakeholder departments, for example, HR or People management (as data owners), IT Operations, IT Support (Service Desk), and the Risk, Compliance and Internal audit departments.
What you need to pay attention to, heavily depends on how HelloID is configured in your organization. For example, if departments are used in business rule conditions (in Provisioning), a structural change of departments in your organization needs to be signaled so that the business rules can be updated in time.
If a design document was created when HelloID was first configured for your organization, you can use it as a reference to understand the configuration and design choices, and identify which components need to be reviewed or updated.
Quick Reference guides help you to find out how HelloID is set up in your organization and quickly locate key configuration details. Use them to get familiar with HelloID and the relevant modules. It is recommended to also use them as a checklist - for example, quarterly - to regularly verify and update settings as your organization’s needs change.