Work on touch devices
Canvas fields distinguish a tap from a drag. Pinch and trackpad gestures should zoom the field rather than the browser page when the pointer is inside the interactive viewport. Mobile side panels use explicit controls and remain dismissible.
Use the expected gesture for the expected action
| Surface | Gesture | Expected behavior |
|---|---|---|
| Teams Canvas or Agent Center | Tap / click | Select or open the object after the pointer has not moved beyond the drag threshold |
| Teams Canvas or Agent Center | Drag | Move the object without opening it first |
| Interactive field | Pinch or trackpad zoom | Zoom objects in the field rather than the entire browser page |
| Library team card | Click | Open one team as the current composition |
| Library team card | Drag onto the field | Add the team to the current composition |
| Mobile side panel | Panel control | Open or close the panel without permanently covering the field |
When Reconnecting appears
- Wait for the connection status to return before making another shared edit.
- The connection banner stays above the header and does not change submenu geometry.
- Saved project and team state is restored from the server after reconnecting.
- A failed static asset must not trigger an automatic full-page reload.
If a page looks incomplete during the first load
- 1Wait for the route to finish
Collty keeps page geometry stable while route styles and authenticated data become ready. Do not repeat the navigation immediately.
- 2Check whether the issue remains
A skeleton may be visible briefly, but raw unstyled controls or a permanently stretched Smart Console are not expected final states.
- 3Reload once
If a network interruption prevented a required asset from loading, reload the current route after connectivity is stable.
- 4Record the cold-load path
When contacting support, include the page you came from, the destination workspace, browser, theme and whether this was the first visit in that session.
If saved data appears missing or stale
| What you changed | When it is persisted | What to check |
|---|---|---|
| Team composition or layout | When the team is saved and when the supported close workflow persists the current layout | Reopen the same saved team, not a different draft |
| Agent state | Immediately for Start, Pause and Stop | The selected project-agent relationship and its current status |
| Agent operating rules | After Settings reports Saved | Unsaved changes do not affect the next run |
| Project participation or hours | After the required role confirms the proposal | Pending values do not replace accepted values |
| Profile data | After the profile passes validation and Save succeeds | The Professional Profile completion boundary and field format |
Chrome and Safari may render effects differently
- Readable content must not depend on backdrop blur. Where Chrome cannot render the intended glass effect reliably, Collty uses a more opaque surface rather than excessive transparency.
- Browser-native search decorations and date/select controls should be replaced or reset where they conflict with the Collty interface.
- Sticky sections depend on the correct page scroll container. A stale modal lock must be removed when navigation leaves the modal route.
- Theme colors, borders and icons should be available on the first load and must not depend on visiting another cabinet first.
Quick checks
- 1Confirm the active workspace
A feature may be available in Team Studio but not in Pro Workspace.
- 2Check project access
Private objects require membership in the relevant project or team.
- 3Retry after reconnecting
Do not duplicate an action while the connection state is uncertain.
- 4Contact support with context
Include the workspace, feature, browser and the action immediately before the issue.
Send a useful support report
- Name the workspace: Client Office, Team Studio or Pro Workspace.
- Name the object or feature: project, team, task, profile, agent or Signal.
- Include browser, device, operating system, theme and approximate viewport size.
- Describe the exact action sequence and whether the issue happens on a cold load, after SPA navigation or after reconnecting.
- Attach a screenshot with private client or project information obscured when it is not required for diagnosis.
- Never send passwords, session cookies, encryption keys or other credentials.