---
title: "Anonymous User Account"
canonical: "https://help.agiloft.com/space/HELP/926908467/Anonymous+User+Account"
format: markdown
---
Not all users are given logins, but in many cases these users still need to access the system to update records. For instance, an external user might not have a login, but they might be allowed to use email hyperlinks that allow them to access the system to update a record, if you enable this in your [Security](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714441) settings. With email updates like these, the system checks the user's email address and tries to match it to a record in the People table to find the user's login. If the system does not find a login or finds no matching record, it logs the user in as the Anonymous User.

The Anonymous User is an actual user in the system with a user record. Users without logins create and edit records under this user. When users without logins make changes to records, the Anonymous User appears in Append Only fields and History fields.

If you send email links to people who are not users, make sure to put the Anonymous User in a group that has the right to view or edit other people's records, and enable the anonymous user to use hotlinks in your Security settings. Otherwise, the user will be unable to view or edit the record if they click the email link. Keep in mind that if you put the Anonymous User in a Power User group, they will use an assigned or floating Power User license.

Do not delete the Anonymous User. Otherwise, users without logins will be unable to access the system.

> ✅ **Best Practice Tip**
> ✅ 
> ✅ If you plan to use email with known external contacts so that they can update or create records, set up user records for them in the External Users table, even if you don’t want them to actually log in to the system.
> ✅ 
> ✅ When a new external user is created, you can have a rule that sets a login by default to their email address and sets a password to a random string. If you don't place them in a group, they will never be able to actually log in to the system. But by giving them a login, you allow the system to better process any changes they make, and you can track these changes in History fields.

#### Related articles

> Macro (contentbylabel)