Invite your team
Your first sign is live on the wall — but Spring Vendor Showcase 2026 has 40 booths and Lakeshore AV has five techs working the floor. Time to bring them into the org so they can claim, monitor, and trigger remote commands from their own phones.
DisplaySync's invite model is two-step: first you invite someone to your organization (controlling org-wide access), then optionally you assign them an event-level role (controlling what they can do at a specific show).
Org-level invites
From the dashboard, go to Organization → Members → "Invite by email".
You'll fill in:
- Email — the address the invitation goes to
- Role — one of owner, admin, or member
| Role | What it grants |
|---|---|
| owner | Full control. Billing, org deletion, transferring ownership. Use sparingly. |
| admin | Everything except billing and deletion. Lakeshore AV's founder gives admin to her two senior techs so they can manage events and members without touching billing. |
| member | Read access at the org level, plus whatever per-event role you assign. Lakeshore's three junior techs start here. |
The invitee receives an email with a link. Clicking it walks them through accepting the invite — if they don't have a DisplaySync account yet, the link doubles as the sign-up flow. Once they accept, they appear in Organization → Members with the role you set.
Pending (unaccepted) invitations show up under Organization → Invitations and can be resent or revoked there.
Per-event roles
Org membership gets someone into the org. Per-event roles control what they can do on a specific event.
From an event's detail page, open the Team tab:
- Add team member — assigns one of your org's members to this specific event
- Role — one of manager or technician (viewer is implicit; see below)
| Role | What it grants at the event level |
|---|---|
| manager | Edit event metadata, manage the team, send remote commands, claim signs |
| technician | Claim signs, send remote commands; cannot edit event metadata or team |
For Spring Vendor Showcase, Lakeshore AV's founder assigns herself as event manager, her two senior techs as managers (so they can also adjust the team if a junior tech is missing), and the three junior techs as technicians.
There's no per-event "viewer" role to assign — read access comes free for every org member, on every event in the org.
Implicit grants worth knowing
This is the part of the model that trips people up:
Org owners and admins are automatically event manager on every event in the org. They don't need to be added to each event's Team tab — the system grants them implicit manager rights everywhere.
For Lakeshore AV that means the founder and her two senior techs (owner + 2 admins) have manager rights on Spring Vendor Showcase, plus any other event the org runs, automatically. The dashboard surfaces these team members with an "implicit" label on the Team tab so you can tell who's there by org role vs. explicit assignment.
The practical upshot: don't bother adding org admins to per-event teams. They're already there.
Mobile app for the team
Anyone you invite can install the DisplaySync mobile app — same TestFlight / Play internal-testing link the engineering team sends out. They sign in with their account, and see the events their roles entitle them to (filtered by org membership and per-event role).
For Lakeshore, the three junior techs install the app, sign in, see Spring Vendor Showcase 2026 in their Events list, and can immediately start claiming signs against it from their phones. See Mobile app for the full feature set.
What's next
You've claimed a sign, set up your team, and threaded everyone into your event. The rest of the docs cover the day-to-day:
- Dashboard tour — what's in the web dashboard and where to find it
- Operating signs — claiming at scale, content assignment, monitoring, remote commands
- Roles & permissions — the full role matrix