Team Management and Project Invites

Team in FieldMarkup is intentionally split into two layers, because the people you work with don't all fit one mold.

• Your company roster: the crew that works for you. Built once in the Business workspace. Carries position, skills, certifications, contact info. Reused on every project you ever do.
• Project guests: sub-contractors, customer IT contacts, vendors, anyone you bring in for ONE job. Invited by email per-project. Never appear in your company roster. View-only or edit access, your call.

This split solves the problem most team tools create: you don't want every sub-contractor you've ever worked with cluttering your team page, and you don't want your roster locked behind a per-seat tax just because you had to email a one-job vendor a link to a PDF.

Open Business → Team. The roster page lists every member of your account. To add someone:

1. Click Add member.
2. Enter their email, name, position, and optional phone.
3. They get an invite email with a link to sign up and join your account.

Once they accept, they appear in the roster as Active. Before they accept, the row shows Invited so you know it's pending.

To remove someone, click their row and use the Remove from roster action. This flips their status to Removed, revokes their access to every project they were assigned to, and preserves the activity history they generated (so an audit of "who edited this plan" still resolves correctly).

Every roster member is assigned one of five positions. The position drives what they can do, on both the project pages they're assigned to and the Business workspace.

Position	Built for	Can edit markup	Sees BOM costs	Manages team
Owner	You, the account holder	Yes	Yes	Yes
Manager	Senior team member with full project access	Yes	Yes	No
Project Manager	PMs running specific projects	Yes	Yes	No
Technician	Field techs installing and documenting	Yes	No	No
Contractor	Read-only field reference	No	No	No

The BOM cost restriction on Technician and Contractor is intentional: unit costs, labor rates, and margins are internal data that shouldn't reach the field crew, let alone an external party.

Click any roster member to open their detail page. There you can tag:

• Skills: a matrix of system categories (CCTV, access, intrusion, fire, network, audio) by capability (install, program). Tick the boxes that apply.
• Certifications: NICET levels, BICSI, manufacturer training, license numbers, with optional expiration dates. The roster surfaces a status pill (Valid, Expiring soon, Expired) so you can spot lapsing creds before they bite you on a bid.
• Phone, notes: contact info and any free-form context (preferred contact time, on-call schedule, etc.).

The Skills tab on the team page lets you filter "show me everyone who can program access," and the Certifications tab gives you a full roster-wide audit of every cert with expirations sorted earliest-first.

On any project page, scroll to the Team section. As the owner you'll see two flows:

• Pick from roster: a dropdown of every active member of your company roster. Pick someone, pick their position on this specific project, and they're added. No email round-trip needed.
• Invite a project guest: enter an email and choose view-only or edit access. The guest gets an invite link scoped to this one project. They never appear in your company roster.

A member's roster position can be overridden per-project (e.g. a Technician on most jobs but acting as PM on one specific build). Roster-level position is the default; per-project assignment wins when set.

The most common team workflow: an owner or PM designs the system (places devices, sets FOV cones, fills in the BOM), assigns Technicians from the roster, and the techs open the project on their phones via the mobile viewer. They update device status as they work (Planned to Wired, Wired to Installed) and snap photos pinned to each device.

The mobile viewer is purpose-built for this. No drawing tools, no clutter. See Mobile field use for the full guide.

Every project has an Activity tab that shows a chronological feed of edits: who placed which devices, who moved or removed them, who finalized a wire run. Edits are grouped by 5-minute windows per user per markup so the feed reads as "Jane placed 4 cameras and 2 readers on the East Wing plan" instead of a flat dump of every pointer event.

Names in the feed come from the team roster (not email addresses) so the audit reads cleanly in front of a customer or auditor.