The Requests pages give leaders a centralized view of all requests submitted across the community. You can filter and sort requests, change their status, edit details, manage the watchlist, discuss a request privately with other leaders, and communicate with residents through comments and file uploads.
Viewing all community requests requires the View Community Requests permission. Without it, members see only their own requests and any they have been added to the watchlist for. Creating, editing, completing, and deleting requests each require their own permission. Some options may be unavailable or appear differently depending on your level of account access.
Log in to Communitrak at https://app.communitrak.com.
In the main navigation menu, expand Requests and click a request type: General, Maintenance, or Architectural.
The page title changes based on the type you selected: General Requests, Maintenance Requests, or Architectural Requests.

Tabs across the top of the page filter requests by status. Each tab shows a count of matching requests.
Pending: Open requests awaiting action.
Completed: Requests that have been resolved.
Approved (architectural only): Architectural requests that have been approved.
Rejected (architectural only): Architectural requests that have been rejected.
Deleted: Requests that have been removed.
Use the search bar to find requests by title, description, ID, or target. Click the filter icon to open the filter panel, which shows a badge with the number of filters you have active:
Type: Filter by All Types, General, Maintenance, or Architectural. This filter is hidden when you are already viewing a specific request type.
Past Due: Show only requests that have passed their deadline.
Watching: Show only requests you are on the watchlist for.
New activity: Show only requests with updates you haven't seen yet.
Target: Filter by All Targets, Property, or Amenity.
Use the Sort by dropdown to order results by Newest First, Oldest First, Title (A-Z), or Title (Z-A). Use Clear Filters to reset the panel. Long lists are paginated, and you can show 12, 24, or 48 requests per page.
Each request appears as a card showing the ticket ID, title, a preview of the description, the target or impact area, key dates, the creator, a status badge, and a watchlist indicator. The card border color reflects the status: yellow for pending, green for completed or approved, red for rejected or past due, and gray for deleted. Click any card to open the detail page.
Click New Request in the top-right corner. This requires the Create Request permission. For details on filling out the form, see the "Submitting and Tracking Requests" article.
Open a request by clicking its card. The detail page shows the full request information and a set of action buttons at the bottom of the main content area.
Complete: Mark the request as resolved. Requires the Complete Request permission.
Edit: Update the title, impact area, description, and deadline. Only available while the request is pending. Requires the Edit Request permission.
Delete: Remove the request. Only available while the request is pending. Requires the Delete Request permission.
Reopen: Return a completed or deleted request to pending status. Requires the Complete Request permission.
Architectural requests replace the Complete button with two separate actions:
Approve: Approve the architectural request. Requires the Complete Request permission.
Reject: Reject the architectural request. Requires the Complete Request permission.
Edit, Delete, and Reopen work the same way as for other request types. Each action asks you to confirm before it is applied.

Below the public comments, leaders see an Internal Discussion card outlined in amber. Notes posted here are never shown to the resident who submitted the request or to the target household.
Use it to coordinate with other leaders, for example agreeing on a position before replying publicly.
To take part, you need the Manage Request Internal Comments permission and you must be on the request's watchlist. If you have the permission but aren't following the request, click Join on the watchlist to unlock the thread.
Click the member count in the card header to see exactly who can read the thread, listed by name and role.
The Watchlist section shows everyone who can view the request and receive notifications about updates such as comments, file uploads, and status changes. It is visible to everyone on the request, including residents, though the management actions are gated.
When a request targets a household, the household members are automatically added and labeled Target Household.
The person who submitted it is labeled Request Creator. Everyone else is a Collaborator.
Click Join to follow the request yourself, or Leave to stop. Joining requires the Join Request Watchlist permission. The creator and target household members cannot leave.
Click Add to search the member directory and add one or more members at once. This requires the Manage Request Watchlist permission.
Click the X beside a collaborator to remove them. The creator and target household members cannot be removed.
Everyone on the watchlist can add comments, and the card header says so. Each comment shows the author, avatar, and timestamp. You can delete your own comments at any time. Leaders with the Manage Request Comments permission can delete any comment.
Everyone on the watchlist can upload files, up to 10 MB each. Supported types include PDF, Word, Excel, PowerPoint, text, CSV, and common image formats. Image files display a thumbnail preview, and each entry shows the file name, size, upload date, and uploader. You can delete your own files at any time. Leaders with the Manage Request Files permission can delete any file.
The Activity timeline shows a chronological log of all changes: opened, updated, completed, approved, rejected, deleted, reopened, comments added or deleted, files uploaded or deleted, and watchlist changes.
When a request has changed since you last opened it, a blue banner at the top summarizes what's new. Click Jump to it to go straight to the new comments or files, which are highlighted in blue.
If your community has AI features enabled, use Summarize above the comments to generate a short summary of a long request thread, and Regenerate to refresh it as the discussion grows.
The Requests module must be enabled in Preferences for the menu items to appear. Each request type (General, Maintenance, Architectural) can be enabled or disabled independently.
Residents without the View Community Requests permission see only their own requests. The list is filtered on the server, not just hidden in the interface.
The Edit, Delete, and Complete buttons only appear while a request is pending.
Reopening a request returns it to pending status regardless of whether it was previously completed, approved, rejected, or deleted.
The notification badge on the Requests menu item reflects the count of pending requests, with a per-type breakdown on each sub-item. A separate dot marks requests with activity you haven't seen.
If your community's account is read-only because of a billing issue, the action buttons are disabled until the account is back in good standing.
If you have questions or need help, chat with Communitrak Support from any page using the messenger icon in the bottom-right corner.