When we originally added support for the Architectural Committee Member user role, we made the decision to make it a "read-only plus some other functionality" user role permission. After overwhelming feedback from our customers, we've pivoted our approach.
Before
A user with Architectural Committee Member role could
- See all property information, including notes, email communications, letters, violations, and escalations
- See all Association information such as inspections, metrics, bulk email/letter communications
- View Architectural Requests and make select changes
They could not:
- Change or add any l property information, including notes, email communications, letters, violations, and escalations
- Change or edit any Association information such as inspections, metrics, bulk email/letter communications
- Send Architectural Request email communications or letters, manage Architectural Request Forms, or initiate new requests
After
A user with Architectural Committee Member role can
- View Architectural Requests, vote, and approve/deny them
- Send Architectural Request email communications or letters
- Manage Architectural Request Forms, or initiate new requests
They can not:
- View, change, or add any l property information not related to Architectural Requests, including notes, email communications, letters, violations, and escalations
- View, change, or edit any Association information such as inspections, metrics, bulk email/letter communications
See our help article on the permissions here.
If these restrictions are not desirable for some of your users; no problem! We'd suggest promoting those users to the Staff or Manager role, depending on your needs.
