This article explains what changes when BrightClient is enabled in BrightManager, what the Bright 'b' logo means, how field validation works, and what is not yet supported in this release.
| Note: BrightClient integration is being rolled out in phases to a selected group of accounts. If you do not yet see the features described in this article, your account may not be enabled yet. Contact Bright Support for more information. |
What has changed in BrightManager
The following areas of BrightManager have been updated as part of this release:
| Area | What has changed |
|---|---|
| Client search | When creating a new client, BrightManager now searches BrightClient automatically as you type, showing matching records from your central repository. |
| Contact search | When adding a Main or Secondary Contact, BrightManager searches BrightClient for existing person records. |
| Email address fields | Email fields have been updated to support BrightClient. You can still add multiple email addresses in a single field, but using the separate additional email fields is recommended to keep your data clean and well-structured. |
| Address fields | Address fields have moved from free-text blocks to separate structured fields (Address Line 1, City, Region, Postcode, etc.). |
| Data synchronisation | Changes saved in BrightManager update BrightClient first, then propagate to all other connected Bright products automatically. |
| Client type | Once a client file has been synced to BrightClient, the client type cannot be changed. |
The Bright 'b' logo — what it means
You will notice a small Bright 'b' logo appearing on the right-hand side of certain fields in BrightManager. This logo indicates that the field is connected to BrightClient — meaning the data in that field is shared across the Bright product suite.
- Fields with the 'b' logo synchronise their data with BrightClient when you save.
- Fields without the logo are local to BrightManager only and do not sync.
Field validation
Fields that connect to BrightClient now include validation to ensure the data meets the standards required for accurate synchronisation. If you enter information that does not meet these requirements, BrightManager will alert you in one of three ways:
| Alert type | Where it appears | What to do |
|---|---|---|
| In-field error message | Directly within the field that has the issue | Correct the value in that field before saving. |
| Toaster notification | A pop-up alert at the bottom of the screen | Review the message, then correct the relevant field. |
| Page-level warning | A summary pop-up covering the full page | Review all flagged fields and correct each one before saving. |
| Note: Validation errors must be resolved before your changes can be saved and synchronised to BrightClient. You will not be able to save and continue until all validation errors are corrected. Exception: address validation errors can be saved locally in BrightManager — your other changes will be saved, but the address will not synchronise to BrightClient until it meets the required format. |
What is not yet supported
BrightClient integration in BrightManager is being delivered in phases. The following are not yet available in this release:
- Self-Assessment and Irish Self-Assessment clients — these client types do not currently synchronise with BrightClient. See Self-Assessment Clients and BrightClient in BrightManager for details.
- Some third-party integrations — BrightPropose, BrightAP, FreeAgent, Xero, QuickBooks, GoProposal, Sage, Zapier, and AIRPA are temporarily unavailable for accounts with BrightClient enabled. These will be restored in a future phase.
- Some system features — the Import Client tool and the Merge Duplicate Individuals feature in the People page are not available while BrightClient is active. These will be addressed in future phases.
If BrightClient is temporarily unavailable
BrightManager is designed to keep you working even if BrightClient is temporarily unreachable. If BrightClient cannot be contacted when you save changes:
- Your changes are saved locally in BrightManager.
- BrightManager will automatically retry the synchronisation in the background.
- You will see a message confirming your changes are saved locally and will sync once connectivity is restored.
Comments
0 comments
Article is closed for comments.