Least-privilege scopes.
Confirm service identities, role boundaries and how a connection is revoked.
Files, customers, access and invoice context should support the work. Explore each intended connection and what still needs to be built.
Track has not shipped yet. Explore the design—not a live product.Scope agreed
Ravi · in review
Approval needed
Delivery status is one view. The cost of delivery is another.
Remaining work, other costs and tax are not included in this snapshot.
Client-view concept: no internal rates, cost totals or private notes. This illustration is not an access-control system.
Existing Centilio products are separate from their future Track connections. Filter the initial scope or later proposals.
15 results
File references and delivery documents. Drive exists separately; the Track connection is proposed.
ExploreCustomer record and agreed scope beside the project.
ExploreInvoiced and paid context, separate from labour cost.
ExploreA shared identity layer with explicit permission boundaries.
ExplorePeople context; rate sources and access still need definition.
ExploreReviewed client updates sent through an agreed email workflow.
ExploreDeadlines and milestones in the calendar; sync direction to be confirmed.
ExploreDirect connectors are a later proposal, not available here.
ExploreA forwarded conversation becomes a task for review.
ExploreField mapping, a small test import and a review before the full move.
ExploreReview exports and attachment references; no lossless import guarantee.
ExploreProjects, tasks, comments, hours and file references in the proposal.
ExploreProposed project and time-entry access; endpoints and auth are not final.
ExploreDirect connectors are later; API availability must be confirmed first.
ExploreA proposed route through Bill, not a direct Track connector.
ExploreNo matches. Clear the search or choose another group.
A shared brand is not a guarantee that every record can be read by every tool.
No executable API examples are published because Track’s endpoints and authentication are not final.
Confirm service identities, role boundaries and how a connection is revoked.
Agree webhook signatures, retries, idempotency and how delivery failures are shown.
Specify field mapping, record ownership and a way to compare source with destination.
The migration design is a starting point, not a claim of lossless import.
0 of 4 reviewed
Personal checklist only. Resets on reload; no approval or request is submitted.
Open a question for the details.
Look closer at the design, or bring us the workflow you need.
Explore the next part of Track.
Explore ↗Explore Centilio’s products and their current release stages.
Explore products ↗Discuss your project workflow. This opens the contact page, not a waitlist signup.
Contact Centilio ↗