Contacts

A person linked to one customer: who you call, who is primary or billing, and optionally who is tied to specific sites. Contacts are not CMS users, not technicians, and not portal logins.

Customers → Contacts · /app/w/{workspace}/contacts · contacts.view / create / update / delete (Archive)

Every contact must belong to a Customer. Veldriq does not create an application user when you save a contact.

What a Contact is

Record	Is it this?
Customer	The organization or person you serve — not a human row in Contacts
Contact	A named person on that customer
Workspace user	Office / dispatcher / technician login (Organization members)
Portal identity	Created only by Invite to portal on the customer — any email, not “this contact”

A contact can be linked to several of that customer’s sites (many-to-many). Site roles (occupant, site manager, …) live on the contact’s Linked sites list — not a separate global Contact role catalog.

Contacts have no tags, custom fields, files, or comments.

Where they are used

• Customer profile → Contacts table
• Service requests and documents can pick a contact (optional)
• Agreements can name a primary and a billing contact
• Field PWA Call / email on the job uses people already on the job or customer

The contact show page lists service requests and activity. Work orders on that page currently show a product placeholder (“Coming in a future release”) — use the customer or work-order screens for job history.

Portal submissions

Portal-created contacts start as Pending review and are not operational until office Approve (or Reject). Actions on the contact list, the contact show page, and the customer’s Pending portal submissions. Permission contacts.update.

Create a contact

Two equivalent paths. Customer is always required.

1. Global: Customers → Contacts → New contact. Or from the customer: open the customer → Contacts → Add contact (customer is prefilled).
2. Customer — searchable select if not prefilled.
3. Status — Active or Inactive when office creates the contact. Portal-created contacts start as Pending review.
4. First name and Last name (required).
5. Job title, Email, Phone, language (optional). Email does not invite the portal.
6. Primary and Billing — customer-level flags. Saving sets at most one primary contact per customer (the product updates the previous primary).
7. Linked sites — transfer list of that customer’s sites. On each site you can set Site role: Occupant, Site manager, Facility manager, Access contact, Property manager, Security, Concierge, Other, and a site-level primary flag.
8. Notes. Save.

Contacts are not portal logins

Invite from the customer’s Customer portal section. Same email as a contact is coincidence, not a link in the database. Public booking may create a contact by email without granting portal access.

Edit, archive, search

Edit from the contact show page. Archive moves the row to Archived contacts. Search: name, email, phone, job title, customer. Filter by Status. Scope with ?customer_id=. Bulk: Archive selected, export selection (no bulk tags).

CSV: Import / Export. Template columns include Customer email or Customer name, First name, Last name, job, email, phone, Primary, Billing, Status, Notes.

What-if

If you cannot save: Customer, First name, Last name required.

If you cannot attach a site from another customer: sites must belong to the same customer.

If you look under Organization members: those are workspace users, not contacts.

Related: Customers, Sites, Portal, concept Contact.