Skip to main content
Open Settings → Business Info → Members. Depending on your team’s configuration, the page has Team Members, Employee Contacts, and Single Sign-On tabs.
Members requires the Members feature and the appropriate settings permission. Single Sign-On appears only for teams with SSO configuration enabled.

Team Members: dashboard access

Use Team Members for people who need to sign in to Avoca. To add someone:
  1. Enter their work email address in the invite form.
  2. Select the least-privileged role that covers their work.
  3. Review any available custom permissions.
  4. Send the invite.
  5. Use the Invited tab to resend or revoke a pending invitation.
Admins with the required permissions can change another member’s role, review or edit permissions, update their display name, and remove them. You cannot change your own role or remove yourself from this page. If ServiceTitan agent mapping is available, link the dashboard member to the correct ServiceTitan agent. Do not use that mapping as a substitute for an Employee Contact record.

Employee Contacts: routing and delivery

Employee Contacts are operational records. A contact can receive calls, texts, emails, reports, on-call broadcasts, or other notifications without needing dashboard access. For each employee, verify:
  • Name, email, and phone number
  • Active status
  • Department and service-area assignments
  • On-call and backup status
  • Relevant email, text, and call preferences
  • Home ZIP when distance-based on-call routing is used
  • CRM employee or technician mapping, when available
You can add contacts manually, sync available ServiceTitan technicians, and use the CSV tools shown on the page. Deactivate a former employee instead of repurposing their record; historical activity can continue to reference it.
Team Members and Employee Contacts are different. Inviting a dashboard user does not automatically make them an alert or on-call recipient, and creating an Employee Contact does not grant dashboard access.

Single Sign-On

The Single Sign-On tab configures SAML SSO through Avoca’s identity service. Coordinate the setup with your identity-provider administrator and Avoca before enforcing it. A safe rollout is:
  1. Configure the SAML connection using the values shown in Avoca and your identity provider.
  2. Add the work email domain that should use the connection.
  3. Complete any requested domain-verification step and confirm the domain shows as verified.
  4. Enable SSO without making it the only sign-in method.
  5. Test with a non-admin user in a private browser session.
  6. Only then enable SSO-only if your organization requires it.
When SSO-only is enabled for a matching domain, email-code and password sign-in are blocked for those users. Keep a tested recovery plan and do not remove the final working administrator until the new configuration is verified.