Contact
A contact is a person attached to a customer (email, phone, role at the account).
Customers → Contacts. Path /app/w/{workspace}/contacts. Permission contacts.view. Customer is always required. First name and Last name are required.
Relationships
Section titled “Relationships”Used for communication and optional picks on requests, documents, and agreements (primary / billing). A contact is not automatically a portal user. Saving a contact does not create a CMS login or a technician.
Primary and Billing are customer-level flags. At most one primary contact per customer.
Linked sites carry a Site role (Occupant, Site manager, Facility manager, Access contact, Property manager, Security, Concierge, Other). Sites must belong to the same customer.
Contacts have no tags, custom fields, files, or comments.
Portal vs booking
Section titled “Portal vs booking”Portal access is Invite to portal on the customer — any email, not “this contact.” Same email as a contact is coincidence. Public booking may create a contact by email; that still is not a portal login.
Portal-created contacts start as Pending review until office Approve.
If you look under Organization members: those are workspace users.
Office manual: Contacts.