Table of Contents
- Homepage views
- Document overview
- Homepage folders
Homepage views provide a quick way to pull up cards based on their relevance to you. Homepage folders allow you to curate and organize cards, either for yourself or as part of a shared workspace with others in the project.
Everlaw remembers the last homepage view or folder you were on, and will return you to that specific page when you next access the homepage.
The default homepage view is “All”, which displays all cards that you have access to across all columns. The exception is searches: in the “All” view, only the most recent 50 searches, and all favorited searches, are shown.
Besides the “All” view, you also have access to views for:
- Favorites: all cards favorited by you
- Mine: all cards created by you
- Shared with me: all cards shared with you
The document overview is a special view that allows you to see pinned data visualizations of your corpus. You can learn more about the document overview in this article.
Homepage folders allow you to organize your work and create shared workspaces. You can add cards into folders and create nested folders for additional structure.
Creating folders and nested homepage folders
You can create new folders from the blue plus button, found in the Folders section of the sidebar and in the toolbar of an open folder.
When creating a new folder, you can select an existing folder to nest under. If the new folder button is accessed from within a folder, the nesting option will be pre-selected with the currently open folder (ie. the new folder will, by default, be added as a subfolder of the currently open folder).
Everlaw supports up to four layers of folders, inclusive of the top-level folder. Each folder layer can contain as many folders as desired.
The folder section of the sidebar displays all folders you have access to. Pinned folders will appear at the top of this section, directly under the filter box. From the sidebar, you can:
- Expand and collapse to view nested folders
- Open folders by clicking on them, and
- Filter folders by name
You can also take action on a folder through the three dot menu icon that appears when hovering over a folder’s name. Available actions will depend on your permissions over the folder.
Clicking a folder on the sidebar will open it for view. At the top left of the folder view, you can see the folder name and a breadcrumb trail that can be used to navigate to other folders above it in the hierarchy. Depending on your permissions, you can rename the folder by clicking on the name and inputting a new name.
Below the folder name is a section that displays all nested subfolders you have access to. And below that are the cards that have been added to the folder, grouped into columns by their type.
The top right of the folder view contains a toolbar where, depending on permissions, you can:
- Create new folders
- Pin the folder
- Select the cards in the folder
- Copy the folder
- Move the folder
- Message users on a folder
- Delete the folder
- Share the folder
- View and modify folder permissions
- Search for all documents associated with cards in the folder
The folder permissions system allows maximum flexibility, making it possible for you to set up private folders within shared folders, or folders with different permissions within the same workspace.
To enable this flexibility, Everlaw treats each folder as an island-unto-itself from a permissions perspective. This means that permissions are not synced between folders, even ones that are nested together. With the exception of some one-time permission inheritance or propagation actions, discussed below, one folder’s permissions will never affect the permissions of other folders.
For the rest of this article, the term “descendent folders” will be used to refer to all folders that exist below a given folder in a hierarchy. In the example below, Folders 2, 3, and 4 are all descendent folders of Folder 1. Folders 3 and 4 are descendent folders of Folder 2. And so on and so forth.
Permissions over folders are either granted automatically upon certain actions, or manually through the share option.
Automatically granted permissions:
- When a folder is created, the creator is automatically granted Full Access permissions on the folder. As the folder’s “owner”, creator’s permissions can never be revoked or modified by other users.
When a folder is nested under another folder, either upon creation or move, the folder will automatically inherit permissions from the parent folder it is being nested under. These inherited permissions are not propagated to descendant folders of the folder being nested.
If there are conflicting permissions (ie. if a user has different permissions on the folder being nested and the new parent folder):
- For folder permissions, the highest of the permissions will be granted
- For object permissions, no inheritance will occur. In other words, if a user has object permissions in the parent folder, but not the folder being nested, the user will be granted the same object permission it has in the parent. If, however, the user already has object permissions in both the parent folder and the folder being nested, it will retain the existing object permission.
- If there are conflicting permissions (ie. if a user has different permissions on the folder being nested and the new parent folder):
Manually granted permissions:
Through the share action, a user with Full Access permissions on a folder can grant new, or update existing, permissions for the folder. The user can optionally propagate these permissions to any nested folders they have Full Access permissions on.
- Note that permissions cannot be revoked through the share action. In practice, this means that if you wish to revoke permissions for a set of folders, you must do so manually, folder-by-folder.
- Through the share action, a user with Full Access permissions on a folder can grant new, or update existing, permissions for the folder. The user can optionally propagate these permissions to any nested folders they have Full Access permissions on.
With the above in mind, the table below outlines the various folder permission levels.
|Folder Permissions||Object Permissions|
|View||Users with this permission can:
||Users with this permission are given view permissions over all cards added to the folder. The exact card actions enabled by this permission depends on the card type.|
|Edit||In addition to the view permissions, users can also:
||Users with this permission are given edit permissions over all cards added to the folder. The exact card actions enabled by this permission depends on the card type.|
|In addition to the edit permissions, users can:
||Users with this permission are given full access permissions over all cards added to the folder. The exact card actions enabled by this permission depends on the card type.|
Viewing folders given permissions
Because of the flexibility of the permission system, users may not have access to all folders in a hierarchy. This has implications for how the folders are displayed to the user. The rule for displaying folders based on permissions is that if a user does not have access to the immediate parent of a folder, the folder will be displayed as a standalone folder for that user.
Imagine a scenario where two users have the following permissions over successively nested folders:
User 1 has:
- Full Access permissions on Folder 1
- Full Access permissions on Folder 2
- Edit permissions on Folder 3
- View permissions on Folder 4
User 2 has:
- Full Access permissions on Folder 1
- None permissions on Folder 2
- View permissions on Folder 3
- Edit permissions on Folder 4
Because User 1 has at least view permissions on all folders in the group, they will be able to see all folders in the group and the full hierarchy will be displayed in the sidebar.
User 2, on the other hand, is not able to view all folders in the group. As a result, the hierarchy chain is broken. This means User 2 will see Folder 1 and Folder 3 as separate top-level folders, with Folder 4 continuing to be nested under Folder 3.
Sharing folders and messaging folder users
If you have Full Access permissions over a folder, you can share it with other users or user groups. To share a folder, click the share button in the folder toolbar.
This will open a dialog where you can select recipients and their folder and object permissions. By default, the option to also share all descendant folders you have Full Access permissions on will be checked, but can be unchecked if you only wish to share the current folder.
Sharing can be used to:
- Grant access and permissions to new users or user groups
- Update the permissions of existing users or user groups
Because you can propagate permission updates to all descendant folders through the share action, this can be used as a one-time sync to standardize permissions for particular users over an entire group of nested folders. Note however that permissions will only be propagated to descendant folders you also have Full Access permissions on.
In addition to sharing the folder, Full Access permissions allows you to message all users on the folder. To message folder users, click the message icon in the toolbar. In the pop-up that appears, you can modify the recipient list and write your message.
You can move folders into other folders as long as the maximum depth of 4 levels is not violated. In order to move a folder, you must:
- Have Full Access permissions over the folder being moved
- Have at least Edit permissions on the new parent folder (ie. the folder being moved into)
Folders can be moved:
- By clicking and dragging in the sidebar. As you drag toward the target folder, it will be highlighted in green. The folder can also be dragged to the “New folder group” area, which will make the folder a top-level folder.
- Via the “move” icon in the folder toolbar. This will open a dialog where you can select the new parent folder to nest the folder under.
If you have at least view permission on a folder, you can copy the folder. The copy dialog can be accessed from the copy icon in the folder toolbar.
Copying a folder will also copy all descendant folders you have permissions over. The logic for which descendant folders are copied mirrors that for displaying folders based on permissions: descendant folders will be copied up until the first break in the chain due to permissions, even if there are folders further down that you have access to.
Copying a folder only copies the folder structure, not the cards that exist in the folder(s).
Moving cards into folders
The option to add a card to a folder is available via the three dot menu icon for a card.
Selecting this option will open a dialog where you can choose the folder(s) you want to add the card to. Cards can only be added to folders that you have at least edit permissions on.
Cards can also be added to folders through multi-select mode, which is activated by long pressing on a card, pressing “x” on the keyboard, or selecting the multi-select icon in the toolbar.
After card selections are made, you can either drag the cards to the folder you want to add them to on the sidebar, or click the “Add to folder” button to open the folder selection dialog.
Note that cards do not exclusively belong in one view or folder. Moving a card into a folder only means it will now appear in the folder, and not that it will be removed from the folder or view you are currently on. This means cards can appear in multiple folders, including folders that are nested together.