Connect an app
Give an employee a real account so it can read and act on the thing itself, instead of working from what you typed.
Connect when a piece of work asks for it. Connecting upfront is how you end up granting scopes nobody uses.
Connect an account you hold
1. Open the employee → Apps
2. Pick the app and authorise it in the window that opens
3. Set the scopes — each one is a switch, allowed or blocked. Hit Disable all and grant back only what the work needs.
Connect an account someone else holds
When the account belongs to a client rather than to you:
1. Open the employee → Apps → Generate connect link
2. Send them the URL. It is secure and time-limited.
3. They authorise their own account. No OpenLabor login is created for them.
Check it actually worked
Ask the employee one real question that can only be answered from the account — "how many unread threads are in that inbox?", "what did we sell yesterday?". A connector that authorised but cannot read comes back vague; a working one comes back with a number.
The app's detail view shows calls over the last 7 days and which skills depend on it, so a silent connector is visible there too.
If a skill refuses to run
That is the intended behaviour: a skill that needs an account says so before it runs rather than returning a confident, empty report. Connect the account it names.
The full catalogue of connectable apps is in Apps. Why accounts sit on an employee rather than on the company is explained here.