> ## Documentation Index > Fetch the complete documentation index at: https://docs.talview.com/llms.txt > Use this file to discover all available pages before exploring further. # What is Not Synced > Some operational data intentionally stays within each organization. Understand what Center Sync does not share between connected organizations. ## Overview Center Sync is designed to mirror **configuration** — the structural definition of a center (its details, rooms, seats, schedules, and workflows). It does not replicate **operational data** — the day-to-day records that belong to each organization's specific exam operations. The following information is **never** synced between organizations: *** ## Proctor and Lead assignments Proctor and lead proctor assignments are **not** synced. Each organization manages its own proctoring staff independently. Your organization's proctor roster is not visible to the partner organization, and vice versa. When the partner organization opens a planning slot, they assign their own team members to it. Capacity tab showing Proctor lead column with + buttons indicating unassigned slots — each organization assigns their own proctors independently This means: * **Your proctor assignments** — visible only in your organization's capacity view * **Partner proctor assignments** — visible only in the partner organization's view * **No crossover** — neither side can see the other's staff assignments through the center interface If you need to coordinate proctor availability or coverage between organizations, use your existing communication channels outside of the platform. *** ## Candidate booking data Candidate bookings are **not** synced. When a candidate registers for an exam at a federated center, the booking record is created in the organization that manages the exam registration — not mirrored to other organizations. Each organization's **candidate list** reflects only the candidates registered through their own workflows. Candidate list view for LRW Schedule 2026-05-23 showing Kim Jims X, Matt TWP, and John 2 Doe 3 with their registration details — this data is visible only within the registering organization This means: * **Your candidate list** — shows only candidates registered through your organization * **Partner candidate list** — shows only candidates registered through the partner organization * **No shared view** — you cannot see partner-side bookings from your center dashboard, and they cannot see yours *** ## Session and check-in data Session records, check-in status, candidate room assignments, and proctor activity logs are **not** synced. These records are produced at the time of the exam session and belong entirely to the organization running that session. They are not copied or visible to connected organizations. *** ## Exam scores and results Assessment outcomes, scores, and result attributes are **not** synced through Center Sync. Each organization retains the results for the candidates it examined. Any cross-organization result sharing is handled through separate integration flows, not through Center Sync. *** ## Where to view this information Even though booking and session data is not visible in the center dashboard of the other organization, **the same operational information is accessible through the Exam module**. | Data type | Where to find it | | ------------------- | ------------------------------------------------------------ | | Candidate bookings | **Coordinator → Exam module** for the relevant tenant | | Proctor assignments | **Capacity → Slot view** within each organization | | Session records | **Session history** in the organization that ran the session | | Check-in data | **In-Center dashboard → Candidate tab** in the relevant org | If you are a coordinator who needs visibility into both organizations' operational data, your platform administrator can grant you access to the **Exam module** on both tenants. This provides a consolidated view of exam logistics without requiring data to be copied between organizations. *** ## Summary table | Data | Synced? | Managed by | | ---------------------------- | ------- | --------------------------------------- | | Center name and details | ✅ Yes | Source organization | | Rooms and seats | ✅ Yes | Source organization | | Schedules and planning slots | ✅ Yes | Source organization | | Workflows and forms | ✅ Yes | Source organization | | Proctor assignments | ❌ No | Each organization independently | | Lead proctor assignments | ❌ No | Each organization independently | | Candidate bookings | ❌ No | Organization where candidate registered | | Check-in and session data | ❌ No | Organization running the session | | Exam results and scores | ❌ No | Organization running the session | *** ## Frequently asked questions Candidate bookings are created and managed by the organization responsible for exam registration. Duplicating booking records across organizations would create conflicting versions of the truth — for example, if a candidate is rebooked or cancelled on one side, the other side's copy would become stale. Keeping bookings within the registering organization avoids this problem and keeps each organization's records authoritative. Visibility into partner-side bookings is available through the **Exam module** on the coordinator tenant, where cross-organization exam logistics are managed. Your platform administrator can configure the appropriate access. Contact your administrator if you need this view. Not through Center Sync. Each organization manages its own user directory and proctor assignments separately. Cross-organization staff management requires a separate configuration or user access setup by your platform administrator. The **Exam module** in the coordinator tenant provides a combined view of scheduling and capacity across connected organizations. Speak with your platform administrator about granting the appropriate access to the relevant team members.