Only an EchoInk User Administrator can grant Habitat access to a user. When a project administrator adds a user who does not have Habitat access, a notification is sent to an EchoInk User Administrator to process the request.
- A Habitat Project Administrator adds a user to a project, which triggers an email to you, the EchoInk User Administrator.
- You receive an email alert that contains a link to the Create New User window, which displays the following information:
- Project administrator’s name
- Project to which the user has been invited
- New user’s email address
- Review and approve the new Habitat user request.
- This action also implicitly grants a new Habitat user access to any Axis Library instance configured for the project. However, an administrator for the project must ensure that the user is explicitly included in the project’s distribution rules.
- If you do not have access to the new user’s employee information, you can contact the project administrator who sent the original invite for more information, outside of the Habitat interface.
- Habitat sends one of the following emails, depending on the user’s Habitat status:
New Habitat user: A Welcome to Habitat email with the subject line New Account Setup for EchoInk Habitat. The user clicks the Go to Habitat button in the email to complete the signup process.
tip Once a user successfully registers his or her account, the Go to Habitat button is deactivated. Instruct your users to bookmark the dashboard URL for their subsequent logins.
- Existing Habitat user: An email with the subject line <project_administrator_name> added you to a Habitat project! The user clicks the project link in the email to join the project as a team member, then logs in with their existing Habitat credentials.