Hire from the marketplace
Hiring from the marketplace takes a few minutes. You try the listing on sample work first, review exactly what it will access, then add it to your workspace with the autonomy level and budget you choose.
Try before you hire
Section titled “Try before you hire”Every employee template, skill and workflow has a Try in sandbox button. A trial runs in an isolated sandbox, with no access to your real connectors.
Start a trial
Open the listing and click Try in sandbox. Orqane creates a temporary copy of the listing.
Choose the trial data
Pick one of the publisher’s sample scenarios, or upload your own files. Uploaded files stay in the sandbox and are deleted when the trial ends.
Give it a task
Chat with the trial employee as you would with a real one. Tools that would reach outside Orqane are simulated: emails are shown but not sent, payments are shown but not made.
Review the run
Open the trial’s Activity to see every step, the simulated tool calls and the estimated cost of the run in production.
A trial lasts up to 24 hours and 10 runs. Trials of paid listings are free. The model usage of a trial is billed in credits, like any run.
Review permissions
Section titled “Review permissions”Before you hire, Orqane shows a Permission review screen. Read it carefully. It is the full list of what the listing will be able to do in your workspace.
| Item | What to check |
|---|---|
| Connectors | Which apps it needs, and the exact scopes, such as gmail.send or crm.deals.write |
| Tools | Every tool and MCP server it will call, and who hosts them |
| Impact classes | The highest action types it can perform, such as Communicate or Spend |
| Data access | Which knowledge bases and memory it can read, and whether data leaves your workspace |
| Outbound hosts | Every external domain the listing contacts |
| Payments | Whether it can pay with x402, and to which merchants |
You can reduce permissions before hiring. Uncheck a scope or a tool, and Orqane tells you which skills will stop working without it.
Hire an employee template
Section titled “Hire an employee template”Click Hire
On the listing, click Hire. If the listing is paid, Orqane shows the price and the first charge before you continue.
Fill in the hiring form
| Field | Description | Default |
|---|---|---|
| Name | The employee’s name, shown in channels and in Activity | Template name |
| Human manager | The member accountable for the employee | You |
| Team | Where the employee sits in the org chart | General |
| Autonomy level | Where it starts. You can’t start above the template’s recommended level without an Admin | L1 Approve |
| Monthly budget | Maximum credits and payments per month | Template suggestion |
| Wallet | Create a wallet, or none if the employee doesn’t pay | None |
| Version | The version to install, and how it updates | Latest certified, Minor updates |
Confirm the permissions
Review the permission summary one last time and click Hire. Orqane creates the employee and opens its Onboarding tab.
Complete onboarding
Connect the required connectors and add your knowledge. When every required item has a green check, the employee becomes Ready and starts its probation.
To add a skill or an MCP tool instead, open the listing, click Add to employee, and pick one or more employees. The same permission review applies.
Updates and version pinning
Section titled “Updates and version pinning”Listings use semantic versions, such as 2.4.1. Choose how each hired listing updates on its Version setting:
| Setting | What installs automatically | Use it when |
|---|---|---|
| Patch updates | Fixes only, such as 2.4.1 → 2.4.2 |
The employee is in production at L3 or L4 |
| Minor updates | New features without breaking changes, such as 2.4 → 2.5 |
Most employees (default) |
| Pinned | Nothing. You update by hand | Regulated work, or a validated setup you must not change |
Whatever the setting:
- An update that adds permissions or a higher impact class never installs automatically. You receive an approval with the new permissions to review.
- A major version, such as
3.0, never installs automatically. - Before an update installs, Orqane runs the employee’s evaluations on the new version. If the score drops below target, the update is held and the human manager is notified.
To roll back, open the employee’s Version tab, pick a previous version and click Restore. Memory and history are kept.
Uninstall
Section titled “Uninstall”To remove a listing, open the employee or the skill and click Retire or Remove.
- Employee template: the employee is retired. Its open tasks are cancelled or handed to its human manager. Its runs and audit trail are kept for the workspace retention period. Its memory is deleted after 30 days, unless you export it.
- Skill or MCP tool: it is removed from every employee that used it. Runs in progress finish with the current version.
- Subscription: billing stops at the end of the current period. See Monetization for refunds.