Contacts panel
Every associated contact, searchable, with a badge showing which team they belong to and whether they are already placed. Select several and place them all at once.
Product tour
Everything Rehnable does
One editor, opened from a HubSpot company record, with two views over the same account: the people inside a company, and the companies inside a group. This page walks through every capability that ships today — and names the ones that do not.
Entry point
A card on the company record, an editor in a modal
Rehnable appears as an app card on HubSpot company records. The card is deliberately thin — a status line and one button — because the rich work happens in the editor it opens, in a modal on top of the record you were already looking at.
You are never asked to log in. The card asks HubSpot to sign the request, our backend verifies that signature, issues a short-lived launch token, and the editor exchanges it for a session. Your identity comes from HubSpot, never from a URL parameter that could be edited.
- No separate account, no password, no second login screen.
- Opens in context — you keep the record, the deal and the timeline underneath.
- Works for every user you have given a seat, with no per-user setup.
People view
The canvas and the contacts panel
The contacts panel on the right lists every contact associated with the company. The canvas holds the hierarchy. Nothing appears on the canvas by accident — you decide who belongs in the chart, which is what keeps a 300-contact account readable.
Pin to canvas
Pinning puts a person on the canvas without giving them a manager yet. It is view state only — pinning never writes anything to HubSpot, so you can plan a structure before committing to it.
Multiple roots and orphans
Real accounts are messy. Rehnable allows several top-level people and treats contacts with no reporting line at all as unplaced rather than forcing a fake single root.
Collapse branches
Fold a manager's subtree to focus on the part of the org you are working on. Collapse state is local to your session and never written to the CRM — and heat colours do not shift when you collapse something.
Selection that works both ways
Selecting on the canvas highlights in the panel and vice versa. Box-select a branch, or use Select all visible, then act on the selection.
Detail panel
Click a card to see the contact's details — properties, buying role, heat score and its inputs — without leaving the chart. Click, never hover, because dragging owns the pointer.
Hierarchy
What actually happens when you drag someone
This is the part most org chart tools get wrong: the structure has to survive outside the tool that drew it.
Stored as a real HubSpot association
HubSpot has no native manager relationship between contacts, so Rehnable creates a custom labelled association pair in your portal — Manager in one direction, Direct report in the other. A reporting line is an association between two contact records, visible on the contact itself, usable in lists and workflows, and yours forever.
Written immediately, undoable immediately
A drop is a write, not a draft — there is no Save button to forget. If it was wrong, Cmd/Ctrl+Z or the undo toast reverses it with a compensating write.
Cycle-safe by construction
You cannot make a person report to their own subordinate. The canvas refuses the drop, and the server validates the same rule again before writing — because the client is never the last line of defence.
Honest about partial failure
Moving someone means archiving one association and creating another. If the second call fails, Rehnable tells you and shows the real state instead of pretending the move succeeded. A silently inconsistent CRM is worse than an error message.
The reporting lines you draw show up on the contact record itself — no Rehnable required to read them.
Placeholders
Chart the role before you know the name
An org chart is sometimes about the position, not yet the person. Add a placeholder for a role no contact fills — the head of procurement you have not met, the decision-maker you know must exist — place it in the hierarchy, and turn it into the real contact once you learn who that is.
A placeholder is a real contact record without an email address, so it behaves like everything else Rehnable creates: standard HubSpot data, in your portal, yours to keep.
How the visual model works
Two independent signals on one card, so you never have to choose between them:
- Background tint = which team the person belongs to.
- Heat = engagement, deals, or the combination.
- Buying role pills = HubSpot's own
hs_buying_rolevalues. - Up to four extra properties = whatever your team decides matters.
Teams
Group people by function, not just by reporting line
Buying committees rarely follow the org chart. Rehnable lets you tag contacts with a
team — Procurement, IT, Finance, whatever you need — stored in a contact property
called orgchart_team that the app creates in your portal.
Because it is an ordinary property, teams are immediately usable everywhere else in HubSpot: list filters, workflow branches, reports.
- Assign a team to many contacts at once as one batch operation.
- Rename or delete a team from the Teams tab; the change propagates.
- Pick a custom colour per team, or let Rehnable derive a stable one from the name.
- Re-parenting never silently changes someone's team — the two are independent.
Workspace actions
Select people on the chart, then do something about it
A stakeholder map that only informs is half a tool. Everything you can see, you can act on — with the selection you made on the canvas, straight into HubSpot.
Create a static list
Turn the selected contacts into a static HubSpot list with a name you choose — ready for a sequence, a campaign, or a workflow enrolment.
Create tasks
One task per selected contact, with a shared title, notes, due date, priority, type and assignee. Ideal for "re-engage every cold stakeholder before the QBR".
Edit properties in bulk
Update the same property on many contacts at once — job title, buying role, or any writable text, number, date or dropdown property. Invalid values are rejected before anything is written.
Remove from the chart
Take someone off the chart without touching the contact record. If that orphans their reports, Rehnable keeps them visible instead of letting them vanish — and the whole thing is undoable.
Bulk means bulk, safely. Every batch action is chunked, rate-limit aware and capped, and Rehnable treats a partial batch failure as a failure you get to see — not as a success with quietly missing rows.
Group view
For accounts that are not one company
Enterprise accounts come as groups: a parent, its subsidiaries, and people scattered across all of them. Flip the People / Group switch and the canvas redraws the corporate structure using HubSpot's own parent and child company associations.
The corporate tree
Parent and child companies as nodes, with breadcrumb navigation up and down the group, so you always know where in the structure you are.
Rolled-up heat
Company nodes carry their own heat — last sales activity and open deal count — so a dormant subsidiary is visible before you drill into it.
Restructure the group
Drag a company under another to set its parent, with the same cycle protection as the people view and a strict one-parent rule enforced on our side.
Search to place
Search the portal for a company that should belong to the group and attach it — no need to leave the editor and go hunting through record pages.
People across the group
A second group view lists the contacts of every company in the group, loaded lazily and built for volume, so you can find the right person across ten legal entities.
Built for real portals
Requests are batched and throttled to stay inside HubSpot's per-portal limits, and unlabelled noise associations are filtered out rather than drawn as phantom edges.
Administration
Settings that a CRM manager actually needs
Seat assignment
Access is granted per named HubSpot user, not first-come-first-served. An admin picks who holds a seat from the portal's real user list, and can move a seat when someone leaves the team.
Card properties
Choose which contact properties appear on the cards — up to four beyond the name — with a searchable picker and drag-to-reorder. Cards grow to fit what you chose.
Team colours
Set a colour per team for your whole portal, stored in your portal configuration, so every user sees the same palette.
Test mode
A switch that runs the editor against built-in sample data instead of your CRM. While it is on, a persistent banner says so — you can never mistake demo data for your real portal.
Self-healing setup
If the association labels or the team property are ever deleted from your portal, the next write detects it, re-creates what is missing and retries — instead of failing and asking you to call support.
Clean uninstall
Uninstalling from HubSpot revokes our authorisation at once, and our copy of your refresh token is deleted as soon as the next token renewal fails — within about half an hour. Everything Rehnable created inside your portal stays in your portal.
Scope
What ships today, and what does not
We would rather tell you what is missing than have you find out during a deal review.
| Capability | Status | Notes |
|---|---|---|
| Org chart with drag-and-drop write-back | Shipping | Company records, contacts associated with the company |
| Heatmap (combined / engagement / deals) | Shipping | Relative to the company you are viewing |
| Teams, colours, bulk assignment | Shipping | Stored as a contact property in your portal |
| Lists, tasks, bulk property editing | Shipping | Datetime properties are excluded from bulk editing for now |
| Company group view and restructuring | Shipping | Group write-back needs the company-write permission granted at install |
| Launch from a contact record | Planned | Today the entry point is the company record |
| Dotted-line / secondary reporting | Planned | One primary manager per person today |
| PNG / PDF export and share links | Not yet | Parked until customers ask for it |
| Live refresh across simultaneous editors | Planned | Reload picks up other people's changes today |
| External org data enrichment | Not planned | Rehnable works on your CRM data, not a third-party database |
See it against your own portal
Early access portals get the full product and a direct line to the person who built it. Tell us your portal ID and what you are trying to map.