Skip to main content

👥 Resident Access Requests

Residents can request access to the community portal at your domain

If a resident needs access and was not part of the initial setup (or was not aware that they were), they can visit your subdomain and request access.

On submission they will see a confirmation popup.

👉 An email will be sent to the default email for your organization and include the details of the request:


👉 Your Board dashboard will show the count of Access Requests awaiting approval.

When you click View, you will be taken to the Access Requests page to approve or deny the request(s)

If you approve, the requesting member will receive a notification back like the below allowing them to complete their account by setting a password.


👀 Requests from an Existing User:

If an existing user sends a request, you can link that request to an existing user to prevent duplication.

👉 Linking the request to someone already in the community

Approving a request can create a brand-new person, or it can attach the request to a person who is already on file (for example someone imported from your old records).

  1. On Access Requests, click Approve.

  2. Confirm the property. Suggested matches appear first. Use Search other properties if the right one is not listed. The dialog shows "Will attach to" once a property is selected.

  3. Under Link to an existing person, review the people at that property.

    • Approve as a new person is selected by default. Use this only when they are not already in the community.

    • If one owner at that property has the same name, that person is selected for you. You can change it.

    • Each person shows their sign-in email. A second line appears when they also have an alternate email.

    • Use Search other people when they belong to the community but are not listed at this property.

  4. Click Approve & attach.

The setup email always goes to the address on the request, even when you link someone whose record has a different address.

If you leave Approve as a new person selected while someone with the same name is already an owner at that property, the dialog warns you that approving will create a second record for them. Link to the existing person instead.

👉 When the resident chooses which email to sign in with

This only happens when you linked the request to an existing person, and that person's record already has a real email that is different from the one on the request.

On the signup page they see "Which email do you want to sign in with?" with two choices:

  • Sign in with the email this link was sent to. This is the address they put on the access request.

  • Keep the email already on my record. Future sign-in mail goes to that address.

The address they do not pick is kept on their record as an alternate email.

If the address on the request already belongs to a different account, that choice is turned off, and "Keep the email already on my record" is selected for them. The note on the page reads: "This address is already used by another account, so it cannot be your sign-in here."

If the two addresses are the same, they are not asked. They finish signup with the email already on the record.

👉 People with no email on file

Imported people who never had an email address show Sign-in: —No Email—.

Link the request to that person, the same way as above. The setup email still goes to the address they entered on the request. They are not asked to choose an email. That address becomes their sign-in email, and the empty spot on their record is filled in. They then set a password and finish signup on the existing person, so you do not end up with two records.

If they still have an older setup link from People, opening that link tells them: "Your community approved an access request for you." They should use the link in the approval email, not the older invite.

🛟 Need more help? Just ask!

Did this answer your question?