Open Subscription Hub to review client status, attention flags and sync context, then open the client or subscription detail only when a record actually needs action.
Before you start
- Know which client or sync issue you are reviewing.
- Decide whether you need a high-level status check or a client-specific action.
- Be careful with any sync-related action because it can affect downstream environments.
Step-by-step guide
- Open Subscription Hub and scan the client list for status, sync and attention indicators.
- Open the specific client or subscription record that needs review.
- Confirm the subscription state, sync health and any pending platform action before saving changes.
- Use related subscription or sync pages only when the client record requires deeper correction.
How to confirm it worked
- The client requiring attention is clearly identified from the hub.
- Any update is performed against the correct client record.
- Sync or subscription actions are verified after they are saved.
Common mistakes
- Changing the wrong client because the list was not checked carefully.
- Running sync-related actions without understanding the impact.
- Treating the hub as a place for bulk changes without reviewing the client detail first.
Do this in Cellivo
Open the live Cellivo screen in the next tab while keeping this answer open here.
More answers
How do I change core branch or company settings?
Open General Settings, confirm the active branch first, update the core business values carefully, save them, then test a dependent workflow such as billing or printing.
How do I add or adjust a payment method used during billing?
Open Payment Methods, create or update the payment option, save it, then confirm the method appears correctly inside Point of Sales.
How do I turn module access on or off for staff?
Use Module Control to enable or disable module visibility for the right role or context, then test the change with the affected user path.
How do I change what a role can do in Cellivo?
Open Role Control, update the permissions for the target role carefully, save them, then test the changed access with a user who belongs to that role.