Services, credits, and ownership
How reusable Services, Yori credits, and ownership fit together, and why each one answers a different question.
ForAll users
On this page4 sections
Three ideas come up again and again in Yori: Services, credits, and ownership. They answer different questions. A Service tells Yori how to do a piece of work, credits decide whether AI work can run, and ownership decides who can see or change something.
Services: how Yori does repeatable work
A Service is a reusable set of instructions for a job you do often, such as a product launch checklist, a blog brief or a monthly report. Instead of explaining the same steps in every chat, you write them once and add the Service to a message when you need it.
Every Service has a main document called SERVICE.md, plus any extra documents and folders you add. Yori reads them when you use the Service in chat.
You'll meet Services from a few places:
| Kind of Service | Where it comes from | Can you edit it? |
|---|---|---|
| Private | You created it or duplicated it | Yes |
| Shared with organisation | You created it and shared it with your team | Yes, you're still the only editor |
| Shared by teammate | A teammate shared it with the organisation | No, it's read-only for you |
| Enterprise-assigned | An Enterprise you work with assigned it to your workspace | No, it's read-only |
| Yori-made | Ready-made Services that come with Yori | No, you can use them in chat but not open their content |
Read Services for the full picture, and Service visibility for who can find each kind.
Credits: whether AI work can run
Yori credits pay for AI work. In the tools covered in this part of the guide, these actions use credits:
- Sending chat messages, including messages that use a Service or a connected app.
- Generating images and videos.
- Each run of an Automation, whether it runs on schedule or you select Run now.
Browsing your library, editing a Service, connecting an app or changing tool switches doesn't use credits.
When your workspace has no credits left, Yori stops the AI action before it starts, so you aren't charged for half-finished work. Everything you've already made stays available. See Out of credits for what still works and how to top up, and Credits and billing for how credits are counted.
Ownership: who can see and change things
Ownership is about the record itself, not your plan or your credit balance. A Business plan can unlock sharing, but it never changes who owns a Service or who can edit it.
| Item | Who owns it | Who else can see it |
|---|---|---|
| A Service you create | You | Teammates, only if you turn on Share with organisation |
| A copy you make with Make a copy | You | Nobody, until you share it |
| A connected app account | You, in the current workspace | Nobody. Teammates connect their own accounts |
| An Automation | You | Nobody else in the workspace |
| Images, videos and references in Image and video | You | Nobody else in the workspace |
Two rules to remember:
- Only the owner can edit a Service. Sharing lets teammates use it and read it, not change it.
- Copying a Service gives you a separate private Service. Later changes to the original don't flow into your copy, and your edits don't affect the original.
For roles, sharing and plan limits across the whole app, see Permissions, ownership, and sharing.