Sales CRM · Feature guide

Resolve account hierarchy access and structure issues

Understand unavailable parents, failed reviews, hierarchy limits and safe relationship repair.

Audience: authorised staffPermission: Sales CRM viewing and native customer access; management permission for repairsReviewed 30 October 2026
Where to goSales CRM → Relationships → Account hierarchy

Before you start

Use your own authorised staff account in the intended Britixo workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.

Follow these steps

  1. Confirm the selected workspace and customer name.
  2. Use Refresh to load current access and relationship information.
  3. Read any Parent path incomplete message and inspect the accessible part of the path.
  4. If authorised to repair the selected customer, choose Change parent and select a verified accessible parent or No parent customer.
  5. Enter the reason, review the change and save it.
  6. Check the resulting hierarchy and history before relying on the repaired structure.

Behavior and limits

  • A customer can become unavailable because it was deleted or your native customer access changed. The hierarchy does not restore access or recreate records.
  • Removing an unavailable parent changes only the selected customer’s stored relationship. Its subsidiaries remain linked.
  • Sales CRM View all does not override native customer access. Managing account hierarchy also requires its separate capability.
  • A user can read a permitted customer’s hierarchy without being allowed to change it. Contact-map management and account-hierarchy management are separate permissions.
  • Read and preview operations do not create account links. Failed saves roll back their relationship and history changes.
  • A preview is tied to the current graph and native company labels. Any relevant change requires a fresh review; do not reuse an old confirmation.
  • Do not infer legal ownership, financial consolidation or access rights solely from the recorded CRM hierarchy. Confirm business relationships using your organisation’s normal process.

Check it worked

  • Check that unavailable customer names and identifiers are not shown in the repaired view.
  • Confirm that existing native customer and contact records remain intact.
  • For removal, check that the customer has no recorded parent and still retains its accessible subsidiaries.

Troubleshooting

  • If Change parent is absent, ask your normal administrator to review the separate capability and existing customer access.
  • If storage is temporarily unavailable, refresh and retry; do not repeatedly submit an uncertain save.
  • If you cannot locate a company, search a more specific part of its existing customer name.
  • If a cycle or depth limit blocks a move, correct the intended company structure rather than repeatedly submitting the same relationship.
  • If another editor is working on the same structure, refresh and coordinate the intended branch moves through your normal workflow.