Skip to main content
Permissions

Understanding how permissions work in PayHOA

M
Written by Michael Bollinger
Updated over a week ago

Broadcast

Read Permission - Gives the user the ability to view all messages that have been sent out via PayHOA.

Edit Permission - Gives the user the ability to craft and send out emails, texts, and phone calls to owners/users in the system.

Budgets

Read Permission – this gives a user the ability to view the Budget overview chart and view the actual budget and chart of accounts. They cannot add or edit the budget.

Edit Permission – This gives the user the ability to create / edit the budget.

Calendar

The calendar is already public to all owners to view, so there is only an edit permission option for the calendar. This would allow a user to write events to the calendar.

Custom Forms

Custom forms work a little differently as each custom form has its own built in permissions.

Read Permission - This gives the user the ability to see all custom forms and all pending or completed forms/requests.

Edit Permission - This allows the user to create new custom forms as well as alter existing ones. They can also view and reply to all form/request types.

Each custom form has its own set of permissions in the "Requests" tab. These can be found under the settings (gear icon) corresponding to each form. Some of the default custom forms that we offer are Architectural, Maintenance, & General Requests.

Architectural Request Form

All owners have the ability to submit architectural requests without any custom permissions. If you don’t want owners to be able to submit these requests, you can disable the form by going to the "Requests" tab, settings (gear icon) for that form, and clicking disable.

Read Permission – this gives a user the ability to view architectural requests for the whole community. They can view the list of requests and each request detail page, but they cannot reply.

Edit Permission – This gives the user the ability to view and reply to Architectural Requests.

There is one more layer of permissions for this module. You can designate who receives architectural request emails by going to Communications à Architectural Requests à Settings. This is completely independent of the Read and Edit permissions and just controls who does and does not receive the request emails from owners.

General Request Form

All owners have the ability to submit General Requests without any custom permissions. If you don’t want owners to be able to submit these requests, you can disable the form by going to the "Requests" tab, settings (gear icon) for that form, and clicking disable.

Read Permission – this gives a user the ability to view General requests for the whole community. They can view the list of requests and each request detail page, but they cannot reply.

Edit Permission – This gives the user the ability to view and reply to General Requests.

There is one more layer of permissions for this module. You can designate who receives general request emails by going to Communications à General Requests à Settings. This is completely independent of the Read and Edit permissions and just controls who does and does not receive the request emails from owners.

Maintenance Request Form

All owners have the ability to submit Maintenance Requests without any custom permissions. If you don’t want owners to be able to submit these requests, you can disable the form by going to the "Requests" tab, settings (gear icon) for that form, and clicking disable.

Read Permission – this gives a user the ability to view Maintenance requests for the whole community. They can view the list of requests and each request detail page, but they cannot reply.

Edit Permission – This gives the user the ability to view and reply to Maintenance Requests.

There is one more layer of permissions for this module. You can designate who receives maintenance request emails by going to Communications à Maintenance Requests à Settings. This is completely independent of the Read and Edit permissions and just controls who does and does not receive the request emails from owners.

Dashboard

The dashboard only has “view permissions” which gives a user the ability to view the HOA’s dashboard. There is not an Edit permission because the dashboard has actions for invoices, owners, units, payments, etc.

Documents

Every owner in the system can view the documents that have been shared with their unit or made “public” in the shared documents section. They don’t need any permissions to view this.

Read Permission – this gives a user the ability to view all the documents for the entire community.

Edit Permission – This gives the user the ability to add / edit / delete documents and folders.


Invoices

Read Permission – this gives a user the ability to view the Invoices page and use the advanced filters to drill down to specific A/R data. They cannot create, edit, or delete invoices.

Edit Permission – This gives the user the ability to add / edit / delete invoices from the account.


Payments

Read Permission – this gives a user the ability to view the Payments page and use the advanced filter to see detailed payment data.

Edit Permission – This gives the user the ability to add / delete offline payments.

People

Read Permission – this gives a user the ability to view the member list and member detail pages. They cannot edit / add / archive users.

Edit Permission – This gives the user the ability to add / edit / archive users.


Reports

Reports only has a read permission. This gives a user the ability to view / generate all reports in the Reports section.

Surveys

Read Permission - this gives a user the ability to view surveys and survey results.

Edit Permission - this gives a user the ability to create, edit, close, and delete surveys.


Transactions

Read Permission – this gives a user the ability to view the Transactions page, but they cannot add / edit / delete transactions.

Edit Permission – This gives the user the ability to add / edit / delete transactions from the ledger.

Units

Read Permission – this gives a user the ability to view the Units page and view the unit detail cards for each unit. This permission does let them view everything on the unit page (account history, invoices, payments, etc.) but they cannot edit anything.

Edit Permission – This gives the user the ability to add or delete units and the ability to edit and add unit tags, custom fields, images, and unit title.

Vendors

Read Permission – this gives a user the ability to view the vendor list, vendor details, and payments that have occurred via Vendors. They cannot edit or add vendors or initiate payments.

Edit Permission – This gives the user the ability to add / edit vendors and initiate payments from the Vendors module. This also gives the user the ability to print checks.

Regardless of having “Edit” permissions, each user has to be authenticated separately via micro-deposits before having Bill Pay ability. This is to ensure that no one can initiate a payment without first verifying they have account access.


Violations

Read Permission – this gives a user the ability to view the Violations list and each individual violation. However, they cannot respond, edit, or create violations.

Edit Permission – This gives the user the ability to add / edit / reply to violations.

Website Builder

Read Permission - This gives the user the ability to view the website without it being published.

Edit Permission - This gives the user the ability to edit, create, and publish the website.

Did this answer your question?