Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.gorelo.io/llms.txt

Use this file to discover all available pages before exploring further.

​
1Password features

​
Vaults

Vaults can be used to restrict access to items for certain groups (and users) in 1Password. There are two common approaches here:
  • Vaults that are based on roles (like L1, L2, Management, Accounts).
  • Vaults that are based on clients (like Acme Corp, Blackrock).

​
1Password tags

1Password uses the concept of tags as opposed to folders for organizational purposes. One of the advantages here is that tags span across all vaults and result in an aggregated list. Folder-like nesting can be achieved with tags by using ‘/’ forward slash. For example, Clients/Acme Corp would result in a top-level tag of clients and then a sub-tag of Acme Corp.

​
Best practice structure for Gorelo

The recommended approach for Gorelo is to follow these steps:
  1. Structure your vaults based on roles, as this offers the most flexibility and scalability.
  2. Organize your vaults by client with tags.
Password items in Gorelo that you have assigned to a client will be tagged in 1Password with Clients/{{client.Name}}. This will allow you to search/navigate using the client name in the native 1Password app, extension, etc. Structuring your vaults based on clients still works. However, it requires you to recreate the service account every time you add a new client/vault, and to map them to groups like “Everyone”.

​
Grant access to 1Password vaults

You can grant access to 1Password vaults similarly in both 1Password and Gorelo.
1Password user> 1Password group> 1Password vault
There is no inherent link between Gorelo users/groups and 1Password users/groups — you will need to configure these independently.