Help someone get their first useful answer
Choose one person and one task they already need to do. You share the models on a machine you run. They use those models from their own app, with their own account and their own application key. Start with that one person; invite the next once it works. You do not need an organization account for a team, a program or a department.
Who does what
| You, sending the invitation | The person you invite | |
|---|---|---|
| Account | Your own | Their own. The invitation page can create one. |
| Machine | Connects it and switches sharing on | Nothing to install |
| Invitation | Sends it, and can withdraw it until it is accepted | Reviews it, then accepts or declines |
| Application key | Does not create or need theirs | Creates their own, one per app |
| Ending access | Pauses or removes them | Stops using your machines, and revokes keys they no longer need |
Accepting your invitation lets them use the models you share. Accepting does not share their machines with you.
Before you start
- A machine that answers. You need a machine connected to your account with a model that has answered a local test. If you do not have one yet, follow Connect your computer and test a model first. If you do, skip it.
- Sharing switched on. On the machine's page in Machines, use the switch beside Sharing is off. Switching it on adds nobody.
- The model they will use. Check that it is in the machine's Models section. If you set sharing hours, pick a time inside them for the first try.
- One task and one example. Choose something small the person needs, and a non-sensitive example of it. The machine that serves a request reads it, so use material that is appropriate for that machine.
1. Invite the person
In Sharing, choose Invite someone.
- One person: enter their email address. The invitation works once.
- A group: one link, with a limit you set on how many people can accept it, up to 100. People who accept the same link cannot use each other's machines through it.
- Expires after: 1, 3 or 7 days.
- Name or note: optional, and only you see it. Use it to recognize the invitation later, for example a team, startup or department name.
If the page says the email did not go out, it shows the link; send it to them yourself. In your own message, say what you are offering, when the machine will be available, and the task you will try first. Never put an application key in an invitation or message.
2. They review and accept
The person opens the invitation:
- Create or sign in to accept creates their account or signs them in with an email link. There is no password to set.
- The page names the account they will accept as. If it is the wrong one, they choose Use another account before accepting.
- They choose Accept invitation, then Use the models shared with you, which opens Applications.
| What they see | What to do |
|---|---|
| This invite has expired, or has been used up | You send a new invitation from Sharing. |
| This invite link can't be redeemed | Check that they opened the whole link, then send a new invitation. |
| They accepted with the wrong account | They choose Stop using on your page in Sharing from that account. You send a new invitation to the right address. |
| Their organization's policy does not allow accepting | They ask whoever manages their organization's Saylek account. |
| They accepted, but you do not see them | Adding a person can take up to a minute. Reload Sharing. |
3. They connect their own app
They follow Get your first answer in an app, starting at its first step: create a key in Applications, enter the connection settings, and choose a model from the list that key returns. The key is theirs. You do not need it, and they should not send it to you. Each app they use gets its own key.
4. Finish a useful task
They send the example task from their app. The step is done when an answer arrives in that app and helps with the task. A saved key, an accepted invitation or a machine that is online does not complete it.
To see which machine served it, open that machine's page in Machines and read its list of requests: it shows when, who and which model. If another machine they can use serves the same model, that machine may have answered instead.
5. Let them return on their own
Have them close the app, open it again and repeat a small task without your help. When something changes later, they can check two places themselves:
- Their Sharing page lists who shares with them and the models they can use now.
- Applications lists their keys, where they can rotate or revoke one.
If they do not get an answer
| Symptom | Who checks | Next check |
|---|---|---|
| Key rejected | They do | Follow the app guide's recovery steps. |
| Their model list is empty | You do | The machine is online with sharing on, you have not paused them, the machine is among the ones you chose for them, and it is inside their shared hours. |
| A model is listed but requests wait or fail | You do | A listing does not hold a place. Check that the machine is serving and not busy, then have them retry. |
| It worked yesterday, not today | Both | They check their Sharing page; you check the machine's page and their page in Sharing. |
Change or end access
On the person's page in Sharing, you can:
- Change machines: choose which of your machines they can use. Machines you share later are not added automatically.
- Shared hours: set the hours they can use each machine, on that machine's clock.
- Pause and Resume: while paused, your machines stop taking their new requests. Each takes effect within about a minute.
- Remove them: only the person who set up the sharing can do this. It applies to their new requests.
To stop shared requests on one machine for everyone, turn off Share from this machine on its page, or run saylek host stop on it. A request that is already running when you remove someone or stop sharing may still finish.
The person can choose Stop using on your page in their Sharing, and revoke keys they no longer need in Applications. A key can also reach other machines they use, so revoke only the ones for apps they are done with. Removing a key from an app does not revoke it.
Scenarios
Every scenario uses the steps above. What changes is who starts, the first task and how it grows.
Help your team use AI
Start here: check Before you start, then invite the person. Invited already? Connect your app.
Who starts: whoever runs the machines, often a founder, CTO or staff engineer. A job title gives no permission in Saylek; the machine's account does.
First task: one colleague asks a chat app to explain an unfamiliar function from your codebase. For a coding agent, follow its own setup and test tool use before relying on it.
Grow it: invite the next colleague the same way. Each person creates a key per tool and can put their own applications in order; that order does not rank one person ahead of another. Work you send to the local API on your machine is taken before waiting shared requests there. If a teammate also runs a machine, they can invite the others to it the same way; accepting one invitation does not share anything back.
Running one app for everyone instead: a team can also run a single application with one key that the application's operator holds. Saylek then sees one account's requests, not each person's: it cannot pause or remove one user, and revoking or rotating that key affects everyone using the app. Who can use the app, and any per-person limits, are the application's own controls. See Set up Saylek for a team.
When someone leaves: remove them in Sharing. If they had a central key, rotate it.
Support startups in your program
Start here: check Before you start, then invite the person. Invited already? Connect your app.
Who starts: whoever runs the program's machines. Start with one person in one startup.
First task: something the startup needs this week, such as organizing interview notes or drafting a support reply, with non-sensitive material.
Grow it: send one-person invitations, or one link for a cohort with a use limit. People who accept do not use each other's machines through your invitation, and you do not need to set the startups up as organizations. Use the note to record which startup an invitation was for, and Change machines or Shared hours to differ by person.
Know the limits: everyone you share with waits for the same machines. Saylek does not reserve capacity for a startup or limit how much each one uses. Keep your own roster of who should have access.
When the program ends: remove each person in Sharing, and withdraw any link that is still open.
Use AI with your family
Start here: check Before you start, then invite the person. Invited already? Connect your app.
Who starts: the family member who runs the machine.
First task: something you do together, such as working through a homework example or planning a trip, in an app they already use.
Grow it: each family member gets their own invitation, account and key. You can help them set up their app. Where their key is kept is a family arrangement; Saylek does not manage it. Use Shared hours to set when they can use the machine.
Know the limits: sharing controls decide who can use a machine and when. They are not parental or content controls. Each person you invite needs an account they are eligible to hold; read who may have one in the Terms of Service before inviting a child.
When it should stop: pause or remove them in Sharing.
Help departments get started
Start here: check Before you start, then invite the person. Invited already? Connect your app.
Who starts: whoever is responsible for the machines. Start with one person in one department and a task with approved material.
First task: a routine task that department already does, such as summarizing a public report.
Grow it: repeat the same invitation for one person in the next department. You do not need to mirror your organization chart; use the note on each invitation to record the department.
When responsibilities change: remove that person in Sharing, then invite whoever takes over.
Share spare capacity
If your main reason is to make a machine you already use available between your own work, start with Share spare capacity, then come back here to invite the first person.
Last checked 2026-10-25 · read as markdown at /docs/help-others-use-ai.md