Stars are stored against your Libra account rather than the browser, so they follow you into any browser you sign in to. The Word and Outlook add-ins are a separate list: their assistant picker has its own **Pin to top** control, saved only on that installation.
## Stars vs. tags
Stars and tags do different jobs. Use both.
| | Star | Tag |
| ----------------------- | ------------------------------------------------------ | ------------------------------------------------------ |
| **What it does** | Sorts a template to the top of the list, just for you. | Labels a template so it can be filtered to. |
| **Personal or shared?** | Personal; only you see your stars. | Shared; anyone who can see the template sees its tags. |
| **How many to use** | Keep it short. A handful, max. | As many as the template warrants. |
| **When to use** | The two or three templates you reach for every week. | Every template, so they're findable in six months. |
## Sharing a template
Sharing a template means being able to change it, so **Share** appears only on templates you own or hold **Edit** or **Full Access** on — open one that was shared with you as **View only** and there is no **Share** control at all. Past that, it depends on your team. If your team doesn't currently have collaboration — you're on a trial, on a plan without it, or the plan was downgraded — **Share** becomes a padlock whose tooltip offers **Enable team features** on a trial and **Upgrade to Team** otherwise. And if collaboration is already part of your plan but you're the only person on your team, **Share** is hidden altogether: there's nobody to add.
When it is available, **Share** opens a dialog with two halves that work independently: a list of named people and groups, and a single team-wide setting.
### Adding people and groups
Type into **Add email, name or group name** and Libra suggests matching team members and user groups; pick as many as you want and they collect as chips in the field. Set the permission for that batch in the dropdown beside it, then press **Add**. The dialog spells out the distinction itself: *Editors can make changes and manage sharing. Viewers have read-only access.*
| Permission | What it allows |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| **View only** (the dropdown calls it *Can view*) | Open and run the template. No changes. |
| **Edit** (*Can edit*) | Change the template, and manage sharing for viewers and editors. |
| **Full Access** (*Full access*) | Everything an editor can do, plus managing the access of people who themselves have **Full Access**. |
You can only hand out a permission you hold yourself, so an editor can add viewers and editors but not grant **Full Access**.
### Team-wide access
Below the invite field, **General access** covers everyone in your team in one setting. **Only people invited** is the default and keeps the template to the list you've built by hand. Switch it to **Everyone in the team** and a permission dropdown appears next to it, so team-wide access can be **View only**, **Edit** or **Full Access** in the same way an individual's can.
### Reviewing who has access
**Who has access** lists the owner, then every person and group you've added, each with its own permission dropdown and a **Remove** action. There is no separate save step — each change is applied as you make it, and the people you added see the template in their library on their next refresh.
