Skip to main content

Sales CRM

Resolve account hierarchy access and structure issues

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

Reviewed 13 November 20262 minute read6 steps

Where to start
Sales → Customer relationships → Account hierarchy

Fields and options

Access needed
Sales CRM viewing and native customer access; management permission for repairs
Permission and scope
Sales CRM viewing and native customer access; management permission for repairs

Before you begin

Open the correct company workspace and confirm Sales CRM viewing and native customer access; management permission for repairs. Review the original record before following these steps. Open the relevant entry under the native Sales menu; the workspace tabs use shorter labels such as Deals, Reports, Relationships and Sales setup.

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.

Check the result

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.

If something does not look right

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.

Fields, rules 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.

Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.