Some checks failed
Frontend / Unit Tests & Coverage (push) Has been skipped
Regenerate POT file (translatable strings) / Regenerate POT file (develop) (push) Failing after 1m13s
Regenerate POT file (translatable strings) / Regenerate POT file (main-hotfix) (push) Failing after 6s
Server / Tests (frappe ${{ matrix.frappe-branch }}) (push) Has been skipped
Server / Resolve frappe matrix (push) Failing after 1s
Frontend / Lint (push) Failing after 1s
Frontend / Production Build (push) Failing after 1s
Server / Coverage Wrap Up (push) Has been skipped
Frontend / Coverage Wrap Up (push) Has been skipped
74 lines
2.5 KiB
Markdown
74 lines
2.5 KiB
Markdown
# User Hierarchy
|
|
|
|
Arrange your sales team into a reporting tree so managers see the leads and
|
|
deals owned by their team, while everyone else sees only their own.
|
|
|
|
Open it from **Settings → User Hierarchy**.
|
|
|
|
## Turning it on
|
|
|
|
The first time you open the page you'll see a prompt to **Enable Sales
|
|
Hierarchy**. Click it to start.
|
|
|
|
While enabled:
|
|
|
|
- Sales Managers see leads and deals owned by themselves and anyone below
|
|
them in the tree.
|
|
- Sales Users see only what they own.
|
|
- Records assigned to someone via a ToDo are also visible up the chain.
|
|
|
|
You can disable it at any time from the same page. Disabling is reversible —
|
|
your tree is kept, so re-enabling restores the same structure.
|
|
|
|
## Adding users
|
|
|
|
Click **Add User** in the top right. A picker opens with everyone who can be
|
|
added — Sales Managers and Sales Users who aren't already in the tree.
|
|
|
|
Pick one or more people and click **Add**. They appear at the top level of
|
|
the tree.
|
|
|
|
To add direct reports under someone, hover over their row and click the
|
|
**+** button. The picker only shows people whose role can report to that
|
|
person (a Sales Manager can have Sales Managers or Sales Users under them; a
|
|
Sales User can have Sales Users under them).
|
|
|
|
## Rearranging the tree
|
|
|
|
Drag a user's row onto another user to make them a direct report of that
|
|
person. While dragging:
|
|
|
|
- A blue line on the target row means the drop is allowed.
|
|
- A faded, struck-through row means the drop isn't allowed — for example,
|
|
trying to put a manager under one of their own reports, or putting a
|
|
higher-ranked role under a lower-ranked one.
|
|
|
|
To move someone back to the top level, open the **⋯** menu on their row and
|
|
choose **Move to top level**.
|
|
|
|
## Removing users
|
|
|
|
Open the **⋯** menu on a row. The options depend on whether the person has
|
|
direct reports:
|
|
|
|
Remove for users with no reports. Takes them out of the tree
|
|
Reassign & remove — moves their direct reports up to their own manager, then removes them
|
|
Remove with reports — removes the user and everyone below them
|
|
|
|
Removing a user from the hierarchy doesn't delete the user from the CRM. It
|
|
just takes them out of the reporting tree, which means visibility rules no
|
|
longer apply to them.
|
|
|
|
## Finding people
|
|
|
|
Use the search box above the tree to filter by name or email. Branches that
|
|
contain a match stay visible so you can see the context.
|
|
|
|
The **Collapse** / **Expand** button on the right toggles all branches at
|
|
once.
|
|
|
|
## Who can edit
|
|
|
|
Only administrators can add, move, or remove users. Everyone else sees the
|
|
tree in read-only mode.
|