Administer Storybuilder Permissions

Storybuilder is Everlaw’s narrative building toolkit. It includes a fact management tool to build your case, an Evidence page to sort and filter your key documents and deposition testimony, collaborative deposition prep and analysis tools, and a collaborative word processing tool, called Drafts. To support your storybuilding, Storybuilder also has Writing Assistant and Deep Dive for transcripts, two generative AI tools to help you analyze your evidence, integrated within it.

This article is for Project Admins to understand how to control access to, and permissions for, Storybuilder tools.

We recommend reading an introduction to Storybuilder before you read this article about configuring it. See our Introduction to Storybuilder article for an overview. 

To learn about some  best practices to configure a Story so your team has a smooth and collaborative narrative building experience, see our Configure Your Story article.

Requirements

All projects on Everlaw come with a Story. The settings described in this article are specifically for Project Admins to set on the Project Settings page. 

Project Settings

Required permissions: Project Admin

The Project Settings page is where you set the user group permissions for granting access to Storybuilder, Writing Assistant, and Deep Dive for transcripts, as well as where you can create and hide Stories. Read on for the details.

Storybuilder Permissions

All Project Admins automatically have Admin permissions on Storybuilder. This allows you to:

• View, edit, and share all Stories in the project
• View, edit, and share all Depositions and Drafts
• View and edit all Fact timelines
• Add documents and document highlights to the Story
• Give Storybuilder access to specific groups in the Permissions page
• Create and hide Stories

To learn how to update the permissions of a user group, see our User Groups and Project Permissions article.

Here is an overview of project level permissions for accessing Storybuilder:

• Receive: Users in this group can receive Stories and any associated Drafts and Depositions explicitly shared with them by others. They cannot access Storybuilder at all until someone has shared the Story, or an object in the Story, with them. 
  When a Story/Deposition/Draft is shared with a user in this group, the user can be given View, Edit, or Full access permissions on the object. 
  When a Draft or Deposition is shared with a user in this group, they are automatically granted View permission on the Story.

• Create: Users in this group with access to the Story are able to create Depositions and Drafts within that Story as well as edit, share, and delete the Depositions and Drafts they have created. 

  Note

  A user with Create permission still requires someone to share a Story or object with them to gain initial access. Once access is granted, the Create permission is additive to the Receive permission, allowing them to create and share their own objects within the shared Story.

• Admin: This is the highest permission a group can have on Storybuilder. Users in a group with Admin permissions on Storybuilder are able to view, edit, and share all Stories in the project. Users in this group can also administer (view, edit, share, and delete) all Depositions and Drafts in the project, regardless of whether the object was shared with them or not.

To learn about permissions for using Everlaw AI Writing Assistant and Deep Dive for transcripts in Storybuilder, see the Everlaw AI tools in Storybuilder section.

Story permissions

Any user in a user group with Receive or Create permission for Storybuilder can have the Project Story shared with them. A Story can be shared with the following permissions:

• View: View the Dashboard, Evidence page, People profiles, Fact timelines, all Deposition transcripts, and any Depositions or Drafts shared with them.
  See the section below for information about how permissions on Depositions or Drafts intersect with Story permissions.
• Edit: Same permissions as View, plus the ability to add and edit evidence and labels on the Evidence page, People profiles, to create and edit Facts and Fact Timelines, and make changes to the Settings that can affect what other users experience in Storybuilder
• Full Access: Same permissions as Edit, and can additionally share the Story with others 

Understand project-level permissions, Story permissions, and object-level permissions

Storybuilder multiple levels of permissions.  

• Project-level permissions: Determine default access to the Story, as described above. These permissions can only be set by a Project Admin.
• Story permissions: For users with Receive or Create project-level permission, the Story permission determines their level of access to the Story. This permission is set when someone shares the Story with a user. 
• Object-level permissions: Determine access to specific objects, such as the ability to view or edit a specific Deposition within Storybuilder. These permissions are granted by a user who created or has full permissions on a given object. Learn more about object permissions in 

As described above, if a user is in a user group with Receive or Create project-level permission for Storybuilder, their permissions on specific objects (Drafts and Depositions) are affected by whether or not someone has shared the Project Story with them, and with what level of access. 

For example, someone in a user group with Receive permission in Storybuilder who is granted Full Access to a specific Deposition is not able to add evidence to the Deposition that is not already on the Evidence page unless they also have Edit or Full Access on the Story. This is because all evidence in a Deposition/Draft is also added it to the Story Evidence page, which requires at least Edit permission on the Story to do. The table below describes some permission combinations and the actions that are allowed and not allowed based on them:

Everlaw AI tools in Storybuilder

Everlaw AI has tools to summarize and analyze your evidence to help you and your team with your Storybuilder goals. If your organization has enabled it, you can configure access to these tools in Project Settings.

To learn more about Writing Assistant functionality, see our Storybuilder and Writing Assistant article.

To learn more about Deep Dive for transcripts, see our Deep Dive for Transcripts article.

Enable Everlaw AI tools in Storybuilder

To enable Writing Assistant and/or Deep Dive for transcripts on a project:

1. Go to Project Management > Project Settings > Everlaw AI.
2. On the relevant section (Deep dive for transcripts  and/or Writing Assistant) switch on the tool.
   

For Deep Dive for transcripts, this starts an ingestion task to ingest all your transcripts in preparation for your team to start asking questions. All future uploaded transcripts are ingested automatically.

Document summaries for Writing Assistant 

Writing Assistant uses AI-generated summaries in its analysis. The summary is the same as that generated through Review Assistant. Storybuilder users with the proper permissions can generate these summaries on a doc-by-doc basis, or you can enable a setting to automatically generate a summary for each document that is added to the Story. To do so, navigate to Project settings > Everlaw AI > Document summaries  page. Then, switch on Automatically summarize new Story objects.

Documents added to Storybuilder via batch action are not auto-summarized, even when this setting is switched on. If your organization has an Everlaw AI contract that enables batch actions, and batch actions are enabled for your project, you can batch summarize any documents that are on your Evidence page and haven't been summarized yet. To do so, in the Existing Story objects without descriptions, select Batch generate summaries .

Everlaw AI Assistant permissions

Permissions for Writing Assistant and Deep Dive for transcripts are in the Everlaw AI section of the Permissions page.

For any user group that you want to enable Writing Assistant for, select Generate, which allows users in that group, who also have Storybuilder access, permission to use the tools.

If there is a user group who should see what Writing Assistant generates, but should not be able to generate on their own, select View.

For Deep Dive for transcripts, the permission levels are:

• None: No access
• Ask: Ask, edit, and delete your own questions
• View and ask: Ask edit, and delete your own questions, and view the questions asked by others

Create a new Story and manage Stories 

Required Permission: Project Administrator 

You can create additional Stories in the Project Settings page or hide existing Stories.

Create a Story

To create a new Story:

1. Go to Project Management   > Project Settings > General > Stories.
2. Select + New Story  and enter the Story name. 
3. Select Create to create the Story.

Hide a Story

To hide a Story, select the eyeball under Show/Hide in project

Hidden Stories have a line through the eyeball . To make it visible again, select the eyeball again. 

You can learn more about creating and managing multiple Stories in the General Settings article in Project settings.

Share a Story

Users in user groups with Receive or Create permission on Storybuilder cannot access the Story until it is shared with them. To share a Story:

1. Go to Storybuilder. To do so, you can select the Storybuilder button on the navigation bar or the Project Story card in the Storybuilder column on your homepage. 
   
   Either of these will take you to the Dashboard.
2. Select Share Story on the bottom left of the navigation panel.
   
   This opens the Share story dialog.
   
3. Select the recipient(s) in the To field. You can choose individual users or an entire user group.

4. Choose the Permission from the dropdown. 
   See the section above for a description of each permission.

   Note

   For anyone in a user group with Create permissions at the project level, sharing the Story also grants them access to create new Depositions or Drafts.

5. [Optional] Edit the Subject line.
6. [Optional] Write a message.
7. When you're done, select Share. This shares the Story with the selected recipient(s).

What's next?

Once you have set up permissions for your Story you can move on to understanding the Dashboard, or creating your first Draft or Fact timeline.