**Note: Lolly Work** This guide covers the optional organisation service. Configuration, console and API paths refer to your Lolly Work instance. The packaged console keeps its release-matched copy of this guide. # Run a partner programme ::: intro This page is for the team that runs partner programmes: resellers, distributors, software partners, service providers or however your organisation groups the companies it works with. Lolly Work gives each partner company your brand, ready to use: the tools, files and templates you choose, filled in with the company's own logos and details. Every file they make records the company it was made for. ::: **Start here:** [Set up a programme](#set-up-a-programme) · [What partners see](#what-partners-see) · [Every option, route and audit event](/info/manage/partner-programmes.html) ## What partners get Partners start with nothing internal. They get what you give their programme and their company, and nothing you share with everyone in your workspace reaches them. Your own people are unaffected, and admins and owners are never narrowed. ::: cards - **[Your brand](/info/manage/partner-shared-assets.html#what-reaches-a-partner)** Your design system's colours, type and palettes, so every tool draws in your brand. - **[Tools](/info/manage/partner-shared-assets.html#choose-its-tools-and-share-its-assets)** Only the tools their programme includes: in the gallery, in search, in server renders and for their agents. - **[Shared assets](/info/manage/partner-shared-assets.html)** Only the files shared with their programme or their company. A file shared with everyone does not reach them. - **[Templates](/info/manage/partner-templates.html)** The templates published to them, on their home and in the tool's **Start** chooser. They change only what you left open. - **[Their company](/info/manage/partner-co-branding.html)** A card for their company at the top of their home, with its logos and details, which fill in every template that takes them. - **[Their agents](/info/manage/partner-agents.html)** A token you issue sees what the company's people see, within limits you set. ::: **Everything a partner gets, and where you set it** | | What a partner gets | Where you set this | | --- | --- | --- | | **To start with** | Your design system's colours, type and palettes, so every tool draws in your brand. No tools, files, announcements or projects meant for your own people. | Built in | | **Tools** | Only the tools their programme includes: in the gallery, in search, in server renders and for their agents. | **Choose what they get** | | **Files** | Only the files shared with their programme or their company: a collection, a folder of a connected source or a file submitted to the programme. A file shared with everyone does not reach them. | **Choose what they get** and **Provider folders** | | **Licences** | When the licence gate is on, only the shared files whose licence lets them be passed on, that your team marked as its own or that someone chose to share anyway. | An administrator's setting, and the programme's **Licences** card | | **Templates** | The templates published to them, on their home and in the tool's **Start** chooser. They change only what you left open; everything else is simply not there, with no note about why. | The programme's **Templates** card | | **Templates only** | Optional, per tool: the tool leaves their gallery, and they make pieces from your templates only. Off by default. | A switch under each template | | **Their company** | A card for their company at the top of their home, with its logos and details. A template that takes company details fills them in, and partners cannot change the ones the template fixes. Named contacts may edit the details. | The company's page | | **What they can do** | Open tools and files, make, save and export pieces, comment, work in projects and make links to what they can see. Admin actions are refused for partners whatever a grant says: editing grants, policy, programmes or the catalog, inviting people, sending messages, making groups and deciding approvals. | Fixed | | **Their files** | Each export's partner record holds the company and programme it was made for, and the revision of the company's details. The record never holds the person, a contact's details, the address, the currency, a token or an agent. | Built in; the export panel's **Design system** card can leave the record out | | **Their agents** | A token you issue sees what the company's people see, within limits you set. | The **Agent tokens** card | | **When they leave** | Access ends at once, or on a date you choose with a notice before. Links they made stop working. | **End this partnership** | ## Four words - A **programme** is your own name for one kind of partner, such as *Resellers, EMEA*. Lolly Work has no fixed list of partner types. - A **company** is one partner organisation in a programme, such as *Northwind IT*. - A **partner** is a person in a programme, or an agent working for one. - A **template** is a ready piece you publish to a programme, such as a product data sheet where a reseller adds only their price. ## How a programme fits together ![How a programme fits together: your design system reaches the programme, the programme gives its tools, assets and templates to each company, each company adds its details, logos and kit, its people and its agent tokens make pieces, and the finished files record the company.](/info/diagrams/work-partners/programme-structure.svg) Your design system comes first: every partner gets its colours, type and palettes. A programme adds the tools, assets and templates you choose, and each company in it adds its own details, logos and kit. The company's people and its agent tokens make pieces from all of that, and each file records the company and programme it was made for. A programme is co-branding: your design system leads, and the partner's mark goes into the artwork as a picture. [Brand architectures](/info/create/brand-architectures.html#co-branding) shows how co-branding relates to the other ways organisations arrange their brands. ## Guides by subject ::: cards - **[Co-branding and partner kits](/info/manage/partner-co-branding.html)** Each company's details, logos and kit, what partners see of their company, and what a co-branded file records. - **[Partner templates](/info/manage/partner-templates.html)** Publish ready pieces, choose what partners may change, keep a tool to its templates and bring out new versions. - **[Partner approvals](/info/manage/partner-approvals.html)** The reviews you can turn on: contact edits, kit changes, agents' requests and one approval for a template's variants. - **[Shared assets and licences](/info/manage/partner-shared-assets.html)** Collections, provider folders, the licence gate, files marked as your own, sharing a held file anyway and credits. - **[Partners' agents](/info/manage/partner-agents.html)** Tokens, scopes, limits and usage, and what an agent reads over your MCP endpoint. - **[People and the partnership](/info/manage/partner-people.html)** Create a programme, check what partners get, invite people, then end a partnership on a date and reopen an end. ::: ## What partners see Rita works at Northwind IT, a company in Resellers, EMEA. ![Rita's home shelf: the Northwind IT card with Details, then the Partner data sheet and a Reseller price list, each with Use](/info/shots/work/partner-home.svg) When she signs in, her home shows: - **Her company card first**, with Northwind IT's logo on your design system's surface and "Your details are on every piece". **Details** shows both logos and every detail. If the brand team named her as a contact who may edit, **Edit** opens the same details with the same checks. - **The templates published to her**, one card each. **Use** starts a piece, **Your copy** goes back to the piece she made last, and **New version** appears on her copy when you publish a newer version. - **The tools her programme includes.** There is no featured banner and no prompt to add personal details, and the only status chip is **Experimental**, because those tools mark their exports as a preview. - **The end of her access**, when there is one. Her company card adds a line such as "Your access through Resellers, EMEA ends on 21 November 2026". - **Her company's kit**, when it has one. New work starts with Northwind IT's kit attached: colours offer the company's colours under its name, the picture picker offers its logos first, and Lolly Design's checks point out a mark smaller than the kit allows or too close to other artwork. A finding is a note to review and never stops an export. Her exports record which revision of the kit was attached. A phone shows the same home in the same order. What she sees inside a template is on [Partner templates](/info/manage/partner-templates.html#what-a-partner-sees-in-a-template), and what her exports record is on [Co-branding and partner kits](/info/manage/partner-co-branding.html#what-a-co-branded-file-records). ## Set up a programme Work in this order. Everything can be changed later. Each step opens its subject page, with the console clicks, the same step with `lw` and, where it helps, the API request. The worked example follows Northwind IT, a reseller in Berlin, into *Resellers, EMEA*, your programme for resellers in Europe, the Middle East and Africa. Rita Ortiz is their sales lead, and your brand team has made a product data sheet in Lolly Design where a reseller adds only a price. Example ids such as `resellers-emea` are yours to choose. ::: timeline - **1. Create the programme.** Name it and set its owning team: here "Resellers, EMEA", run by `partner-team`. [People and the partnership →](/info/manage/partner-people.html#create-the-programme) - **2. Choose its tools and share its assets.** Here **Certificate**, **QR Code** and the **Logos for partners** collection. [Shared assets and licences →](/info/manage/partner-shared-assets.html#choose-its-tools-and-share-its-assets) - **3. Add the companies and their details.** Northwind IT's website, contact, address, currency, tax note and logos. [Co-branding and partner kits →](/info/manage/partner-co-branding.html#add-a-company-and-its-details) - **4. Publish templates.** The data sheet, with its logo and details line taken from the company. [Partner templates →](/info/manage/partner-templates.html#publish-a-template) - **5. Check what they get.** Preview Northwind IT as its people get it, and open the app as a partner, before anyone is invited. [People and the partnership →](/info/manage/partner-people.html#check-what-they-get) - **6. Invite the people.** Rita, by list, with Northwind IT as her company. [People and the partnership →](/info/manage/partner-people.html#invite-the-people) - **7. Give Rita's agent a token.** The default scopes and limits, for 90 days. [Partners' agents →](/info/manage/partner-agents.html#give-an-agent-a-token) - **8. End the partnership on a date.** Northwind IT alone, on 30 June 2027, with a notice. [People and the partnership →](/info/manage/partner-people.html#end-on-a-date) ::: ## Day to day - **A new version of a template, or retiring one:** [New versions and retiring](/info/manage/partner-templates.html#new-versions-and-retiring). - **A company's details change:** [Change a company's details](/info/manage/partner-co-branding.html#change-a-company-s-details). - **A partner in two programmes:** [A person in two programmes](/info/manage/partner-people.html#a-person-in-two-programmes). - **A file the licence gate holds back:** [The licence gate](/info/manage/partner-shared-assets.html#the-licence-gate). - **Checking a limit:** [Limits and quotas](/info/manage/partner-people.html#limits-and-quotas). - **Ending a partnership, ending on a date or undoing an end:** [End a partnership](/info/manage/partner-people.html#end-a-partnership). ## Related - Every option, route and audit event: [Partner programmes](/info/manage/partner-programmes.html) - Locking inputs for a programme or a company: [Policy and governance](/info/manage/governance.html) - Who can do what: [Roles and grants](/info/manage/permissions.html) - Co-branding in the app: [Working with partners](/info/create/partners.html) - Reading a file's record: [What Lolly Verify checks](/info/trust/what-verify-checks.html) --- Content ([MPL 2.0](https://www.mozilla.org/en-US/MPL/2.0/)) · [Lolly Work source](https://github.com/lolly-tools/lolly-work/tree/36414f800798deb30d0cf7c6e6712d0205c6931d) · [lolly.tools](https://lolly.tools)