Teams

Use teams to control branding, reminders, sender configuration, and other team-level settings before you create inspections.

What a team controls

A team is the top-level configuration object for inspections. When you create an inspection, you pass a team_id, and that team determines the customer-facing branding and team-level settings used for that inspection.

Teams control:

• Branding — the logo and colors customers see in the inspection app
• Reminder schedules — start and finish reminders that encourage customers to complete inspections
• Team-specific configuration — defaults and settings that apply to inspections created under that team

If your organization supports multiple brands, business units, or workflows, use separate teams so each inspection uses the right branding and communication settings.

Create a team

Create a new team when inspections need separate branding, sender configuration, reminder schedules, or other team-level settings.

1. Choose the template team the new team should start from.
2. Decide whether to copy user assignments and inspection type assignments from that template.
3. Create the team and save the returned team_id.
4. Upload a new logo or icon if the new team needs different customer-facing branding.

Use Create a team for the exact request body and response schema.

Choosing a template team

Every new team starts from a template team. The template determines the starting configuration for the new team, including branding and other team-level settings.

• If you pass a template template_team_id, the new team copies that team's configuration.
• If you do not pass a template template_team_id, Vision uses the first team created for your organization.

Choose the template team intentionally when your organization supports multiple brands, workflows, or operating groups. Starting from the right template can reduce follow-up updates after the team is created.

Decide what to copy from the template

When you create a team, you can also copy assignments from the template so the new team is ready to use sooner.

If the new team is for a different operating group, brand, or workflow, decide whether these assignments should stay separate instead of being copied.

Update a team

Use PUT /v3/organization-teams/{teamId} to change team settings after the team is created.

Use this endpoint to update branding and operational configuration. Reminder schedules use the same endpoint, but they are broken out in the next section so you can review that behavior separately.

Update branding settings

API integrators can use this endpoint to update these customer-facing branding fields:

Update team configuration

API integrators can use this endpoint to update these operational settings:

Use this endpoint for team settings that API integrators are allowed to manage directly. Some additional team fields can only be updated by Truepic. If you need to change a field that is not listed here, reach out to Truepic.

Configure reminder schedules

Reminder schedules are also configured at the team level.

• Start reminders are based on when the inspection was sent. They send only for inspections that have not been started.
• Finish reminders are based on the amount of time remaining before the inspection expires. They send only for inspections that have been started.
• You can configure multiple reminders of each type. Because reminders to start only get sent before an inspection has been started, and reminders to finish only get sent after the inspection has started, their schedules can overlap some.

Use these fields when you update reminder schedules:

Set a cadence that matches your inspection window and customer behavior. Well-timed reminders can help more customers start and finish inspections before they expire.

Update branding assets

If the team needs different customer-facing branding, upload a new logo or icon after the team is created. This is useful when the template gives you the right starting configuration but the new team needs its own visual identity.

Asset requirements:

• PNG only
• Max 1 MB
• Logo: at least 369x102
• Icon: at least 180x180

Use Upload team assets to replace the team's branding assets.

Use the team when you create inspections

Once the team is configured, pass its team_id when you create inspections.

{
  "team_id": 123,
  "inspection_type_id": 123456,
  "customer_first_name": "Philip",
  "customer_last_name": "Graham",
  "custom_field_values": ["abc123"],
  "send_methods": {
    "text": true,
    "email": false
  },
  "customer_phone_number": "5555555555",
  "include_list": true
}

When to create multiple teams

Create multiple teams when different inspections need different branding or operational settings. Common reasons include:

• supporting multiple business units
• separating customer experiences by product line or region
• keeping internal configuration isolated by team

Team API reference

Use the API reference when you need the exact request and response schema for a specific team operation.

• Get a list of teams
• Get a team
• Create a team
• Update team
• Upload team assets

What to read next