Your organisation can run its own Lolly: the same app, with the tools and design systems it chose. Find out how to reach it, sign in and what changes.
For planning the organisation's setup, Use Lolly with your existing DAM explains how an approved library can stay in place while people make content in Lolly. Content sovereignty describes the wider control over creation, governance, storage and portability.
The web address of its Lolly, or a .lolly setup file your organisation made. lolly.tools on its own does not connect to an organisation.
In a browser
Open the address your organisation gave you. If the page asks you to sign in, press Sign in and follow the sign-in page it opens. After that, Lolly works as usual, with your organisation's tools and design systems.
You can also start from lolly.tools: open the Settings view, and on the Lolly instance card press Open a workspace, enter the address and press Open this instance. The browser goes to your organisation's own address, because a browser cannot load another Lolly's tools from lolly.tools.
signed by Lollyvector SVG8 paths~2.9k nodes13 groups35 KBCheck it yourselfGet the signed file
signed by Lollyvector SVG8 paths~2.9k nodes13 groups35 KBCheck it yourselfGet the signed file
In the desktop or mobile app
The app starts with its bundled tools. To connect, open the Settings view and press Change on the Lolly instance card. The sheet asks Where should Lolly get its tools?
- Choose Connect to a Lolly instance.
- Enter your organisation's web address and press Check & connect.
- Press Use this instance. The next screen, Import your data (optional), brings saved work across from a Lolly backup. Press Skip if you have none.
- Sign in if the app asks.
Tools from a connected instance run with the same trust as the app's own, so connect only to one you trust. Your organisation may instead send you a .lolly setup file that connects the app for you.
To switch later, use Change again, or Leave on the same card.
Signing in with a code
In the desktop and mobile apps, the sign-in screen also offers a short code when your organisation's Lolly supports code sign-in. Press Open sign-in in browser, sign in and approve the code there. Or open the address the screen shows on a phone or computer where you are already signed in, and enter the code. The code lasts about ten minutes.
What is different there
- Some controls are set for you. A control your organisation governs shows Managed by and the organisation's name, or Managed by your organisation. A fixed control cannot be changed, and a menu may offer only some of its choices. Some controls are hidden. Your organisation's console records which rule fixed a control and why. Ask whoever runs your organisation's Lolly.
- Some design systems are locked. A design system your organisation supplies shows a lock and stays read-only. To try changes, make an editable copy in Settings → Preferences → Design systems.
- Only its tools are listed. A tool your organisation does not offer is not shown.
- Shared projects. If your organisation shares projects with you, Projects shows a Team projects tile. These sessions live on the organisation's server. Open one to work on it, or start a work collab from Share when available.
- Some exports may need approval. Where your organisation asks for approval, Request approval takes the place of Download, and a tool may offer fewer formats.
- Your home may open on templates. If your organisation publishes templates to you, as it might for a partner company, your home opens on them instead of the first-visit greeting. Each template is one card, with Your copy to carry on and New version when the template changes. See Partner templates.
What stays where
On this device
- Your own saves, unless you turn on Sync
- Design systems you made yourself
- Anything you make and download
On your organisation's server
- Your sign-in identity and device information
- Team projects, shared sessions and live edits in a work collab
- Assets you upload to the shared library
- Approval requests and approved deliveries
- A log of your sign-ins and what you do there
With a workspace connected, the privacy line on the app's first screen says the same. Lolly's own apps send the workspace no usage events. Privacy lists what the server stores and who controls that data.
What Lolly Work adds
Your organisation's server runs Lolly Work, the organisation software of the same open-source project. The app needs neither a work account nor Lolly Work when you use it on your own.
What Lolly Work can add
Your organisation hosts Lolly Work alongside Lolly and chooses which features to turn on:
- Sign-in and access. Organisation single sign-on, group-based permissions and managed profile fields. Administrators can provision and deactivate accounts through SCIM.
- Shared work. Team projects, shared sessions and work collabs, with live editing through the organisation's server.
- A shared asset library. Uploaded assets, collections and connected libraries, with access rules, versions and review.
- Review and delivery. Approval steps, managed links with expiry or revocation, and delivery to destinations the organisation permits.
- Administration. An audit record of governed actions, and usage reporting under the instance's telemetry policy for clients that send usage events. Lolly's own apps send none today.
To set up the service, start with Deployment. The public demo at lolly.work is a sandbox. Use your organisation's own address for work you need to keep.
Another organisation's brand
A partner, client or sponsor may send you their brand as a design-system file (.lolly) instead of an address. Opening that file connects the app to nothing. The file adds their design system beside your own on this device. A setup file from your own organisation connects the app to the organisation's Lolly. Before anything changes, the preview shows what opening a file will do. Working with partners covers both sides of working in another organisation's brand.
Leaving
Leave, on the Lolly instance card in Settings, removes your organisation's design system, tools and catalogue. Your own work stays. Anything you made with its tools will not open again until you reconnect. Where your organisation's Lolly offers it, Sign out everywhere on the same card ends your sessions on every device, this one included.
Anything you saved to the organisation stays with the organisation, under its access and retention policies. Leaving or clearing this device does not delete that server copy. In a browser at your organisation's own address there is nothing to leave: open a different address instead.
Who to ask
What reaches your organisation's server, who can see its shared projects and which settings are fixed are your organisation's decisions. Ask whoever runs your organisation's Lolly. Privacy covers what Lolly itself does with your data.