Skip to main content

Dashboard vs Resident App: What lives where

This article helps Admins quickly work out whether something is done in the Admin Dashboard or in the resident app, and what the practical limits are.

Michael Agius avatar
Written by Michael Agius
Updated over a month ago

The two surfaces

Admin Dashboard

Often referred to as the Control panel, the dashboard is for staff operations. It is the control panel for a site, or for a portfolio if you are a super admin.
​

Resident app

The app (which is accessible for free via the App Stores) is for resident participation. Residents receive information, submit requests, respond to invitations, and use community features.


What staff do in the Admin Dashboard

People and access

  • Create and manage staff users

  • Assign roles and permissions

  • Assign site access for staff who cover multiple villages

  • Reset passwords and deactivate staff, based on permissions

Residents and profiles

  • Create and manage resident profiles (members)

  • Maintain resident contact details used for email and SMS escalation

  • Add and update resident addresses

  • Link family members

  • Set resident privacy controls for the resident directory

Communication

  • Create broadcast channels

  • Send broadcasts:

    • in app announcements

    • email escalation

    • SMS escalation (if enabled)

  • Manage when messaging is one way versus two way

Events, facilities, and bookings

  • Create events, including repeating events

  • Add attachments and online meeting links

  • Create facilities and set booking rules

  • Approve or decline facility bookings

Requests and workflows

  • View and manage requests submitted by residents

  • Create requests on behalf of residents

  • Approve or reject pending requests

  • Progress requests through statuses

  • Assign staff or service providers

  • Add internal notes and resident updates

  • Archive requests

  • Export data

Content and documents

  • Upload documents to the library

  • Publish newsfeed articles with images and attachments

  • Target content by tags or roles, where configured

  • Promote content via broadcasts

Surveys, forms, and feedback (if enabled)

  • Create surveys and review results

  • Create connected forms and link them to requests, where configured

  • Configure and process feedback capture items


What residents do in the app

Receive information

  • Receive broadcasts

  • Read newsfeed articles

  • Access documents published to them

Participate

  • View events

  • Accept or decline invitations where RSVP is enabled

  • Request facility bookings, where enabled

Submit and respond

  • Submit maintenance or gardening requests, where enabled

  • Attach photos and descriptions to requests

  • Complete surveys and forms

  • Submit feedback capture entries, where enabled

Messaging

  • Residents can create private resident to resident conversations

  • Admins cannot view private resident chats


Practical rules to avoid confusion

Broadcasts vs conversations

  • Broadcasts are one way. Residents cannot reply.

  • Conversations are two way. Residents can reply.

Use broadcasts for announcements. Use conversations only when you want replies. Generally Conpago
​

Not everything triggers notifications

  • New events do not notify everyone by default. This avoids spam.

  • Bookings and request updates generally notify the resident involved.

  • Documents and news often rely on broadcasts to drive awareness.

Default locations can be misleading

Maintenance & Gardening Requests default to the assigned resident's address. If the job is in a common area, override the location when creating the request.


Quick decision guide

Use the Admin Dashboard when you need to:

  • manage staff access, roles, or modules

  • manage resident data and privacy

  • approve bookings or requests

  • publish content and run broadcasts

  • report and export

Use the resident app when the resident needs to:

  • receive information

  • request something

  • RSVP

  • complete a form or survey


Related articles

  • Conpago structure: sites, staff, members, addresses, family, tags

  • Roles and permissions in Conpago

  • Messaging: broadcasts vs conversations

  • Requests overview and lifecycle

  • Events and bookings: overview

Did this answer your question?