1. Your dashboard
Go to /my/partner-dashboard. Summary cards show your opportunities, databases, clients, access requests and AI token usage, plus the nodes assigned to you and their availability. From there you reach every page of the partner portal:
| Page | Route | What it's for |
| Databases | /my/partner-databases | Your clients' databases |
| Clients | /my/partner-clients | Your client contacts |
| Accesses | /my/partner-accesses | Your access requests |
| Tokens | /my/partner-tokens | AI token usage |
| Nodes | /my/partner-nodes | Your nodes and their availability |
| Credentials | /my/partner-credentials | Your access credential |
You only see what's assigned to you. Every page shows your clients' databases, never another partner's, and each action checks ownership again before it runs.
2. Opportunities
Go to /my/partner-dashboard/create-opportunity. You create an opportunity that's assigned to you, tagged as your own lead and linked to the right sales rep at Binhex Cloud.
The opportunity is the mandatory starting point for creating a database: the creation form asks you to pick an existing opportunity.
3. Your clients' databases
Go to /my/partner-databases. The list gives you these tools:
| Tool | Options |
| Search | Free text |
| Sort | Date · Name · Status |
| Filters | Running · Stopped · Creating · Not created · Ready · No hostname |
| Group by | Client |
Click a database to open its page.
4. Create a database
Go to /my/partner-databases/new.
Requires: an existing opportunity (see section 2).
Steps
- Choose the opportunity the database comes from.
- Choose the plan or bundle.
- Enter the client's company name.
- Choose the hostname, region and language.
- Enter the client contact. If it doesn't exist yet, it's created, and you'll need the client's email.
- Confirm.
Required fields: plan, opportunity, company name and hostname. The form won't continue without them.
What happens next
- The platform checks that you haven't reached your database limit.
- If the client contact doesn't exist, it's created.
- If the client already has a password, the subscription and the database are created on one of your available nodes, and setup starts right away.
- If the client doesn't have a password yet, the database is put on hold and the client receives an invitation by email.
Deferred setup
When the client hasn't set a password yet, the database isn't created right away. As soon as the client sets their first password, setup continues on its own.
This is expected, not an error: the database shows an earlier status until the client acts. If you need it sooner, you can set the password for them from your clients page (see section 7).
Delete a database
Use /my/partner-databases/[id]/delete.
Only possible while the database is Not created. Once it's created, the client has to request its removal from their portal, or the Binhex Cloud team has to do it.
5. Stop and start with a reason
| Action | Route |
| Stop | /my/partner-databases/[id]/stop-partner |
| Start | /my/partner-databases/[id]/start-partner |
Unlike the customer portal, here you record a reason. Write it with care: it's what the Binhex Cloud team, and the client, will see if they ask why the database is stopped.
Stopping a database cuts off the client's users immediately. Let them know before you do it.
6. Propose an upgrade
Go to /my/partner-databases/[id]/upgrade.
- Choose the new plan.
- A quote is generated for the client.
- The quote is emailed to the client automatically.
You propose, the client accepts. When the order is confirmed, the new plan is applied.
If something fails: you're sent back to the database page with ?error=no_product. It means the plan you chose isn't valid for an upgrade.
7. Your clients
| Action | Route | Details |
| List contacts | /my/partner-clients | Your client contacts |
| Create a contact from a lead | /my/partner-clients/create-contact | Takes the name and email from the lead |
| Set a client's password | /my/partner-clients/set-password | It must meet the password policy |
Setting a client's password is a sensitive action. Use it to unblock a deferred setup, or when the client asks you to, and share the password through a secure channel. As soon as you set it, any database on hold waiting for that password starts its setup on its own.
8. Your nodes
Go to /my/partner-nodes to see the nodes (servers) assigned to you and their availability. Check it before promising a new database, to make sure you have capacity.
A node can only be assigned to one partner. If a node you expected isn't listed, it's assigned to someone else.
9. Access to client databases
Being a client's partner doesn't give you access to their database: you have to request it, and the client has to approve it.
Steps
- Click Request access on the database's page (
/my/partner-databases/[id]/request-access). - The request is created with your access credential (see section 11). If you already have a request for that database, no duplicate is created.
- The client receives the request and approves or refuses it.
- Once it's approved, you can sign in to the client's Odoo database with your credential.
In /my/partner-accesses your requests are grouped into approved, pending and cancelled or revoked.
Access expires. Its expiry date can't go beyond the expiry of the client's database. When it expires, the platform removes it automatically and lets you know.
10. AI token usage
Go to /my/partner-tokens, or open a specific database from there. You'll see AI token usage per database and per user, with a date filter and a chart.
Use it to:
- Spot a client who's about to run out of credits, before their agents stop.
- Back up a credit sale with real data.
- See which of the client's users consumes the most.
11. Your access credential
Go to /my/partner-credentials to set and change your own LDAP password. It's the credential you use to sign in to your clients' databases once they approve your access.
- You have one credential, not one per client.
- Your login is generated automatically from your user and the platform's email domain.
- Changing your password here changes it for every database you have approved access to, because sign-in is centralized.
If this credential is compromised, change it immediately. It gives access to every database you've been approved for.
12. Commissions
When you create a database, you're registered as the agent of that client contact. That's what allows your commission on their sales to be settled.
There's no commissions page in the partner portal: ask your sales contact at Binhex Cloud.
13. Portal errors
The partner portal reports errors through a parameter in the URL. These are the ones you may see:
| Parameter | It means | What to do |
?error=container_limit | You've reached your database limit | Ask Binhex Cloud to raise it |
?error=missing_email | You tried to create a new contact without an email | Enter the client's email |
?error=no_product | The plan you chose isn't valid for that operation | Choose a different plan, or contact Binhex Cloud |
?error_msg=[text] | A specific error during creation | The text is the cause. If it isn't clear, contact Binhex Cloud |
14. Troubleshooting
| Symptom | Likely cause | What to do |
| A new database doesn't start and stays in an earlier status | The client hasn't set their password yet | Set it from /my/partner-clients/set-password, or remind the client about the invitation |
| I can't delete a database | It's already created. Deleting is only possible while Not created | Ask Binhex Cloud, or have the client request it from their portal |
| A node I expected isn't listed | It's assigned to another partner | Check with Binhex Cloud |
| The client says they can't start their database | An overdue invoice on their subscription | It starts again automatically once the invoice is paid |
| I requested access and can't sign in | The client hasn't approved it yet, or it expired | Check /my/partner-accesses |
| The upgrade quote didn't reach the client | An email configuration issue on our side | Let Binhex Cloud know |
| A client's AI agents have stopped | They ran out of credits | Sell them credits: the agents turn back on once topped up |
15. Quick reference
| Page | Route |
| Dashboard | /my/partner-dashboard |
| Create an opportunity | /my/partner-dashboard/create-opportunity |
| Databases | /my/partner-databases |
| Create a database | /my/partner-databases/new |
| Stop / start | /my/partner-databases/[id]/stop-partner · /start-partner |
| Delete (only while Not created) | /my/partner-databases/[id]/delete |
| Upgrade | /my/partner-databases/[id]/upgrade |
| Request access | /my/partner-databases/[id]/request-access |
| Clients | /my/partner-clients |
| Nodes | /my/partner-nodes |
| Access credential | /my/partner-credentials |
| AI token usage | /my/partner-tokens |
| Access requests | /my/partner-accesses |