Skip to main content

Admin guide to LawVu Draft

A structured overview of admin tools and responsibilities

K
Written by Kim Nichols
Updated today

Learn about context on the settings available to administrators in LawVu Draft. Each section explains how a set of tools fits together; click on linked tools for quick setup.


1. Access control and permissions

Decide who can see, use, edit, or manage content.

These tools are about authorization, not user accounts themselves.

Controls what actions users or groups can take on specific content.

  • Define read, use, edit, and create permissions

  • Apply to Playbooks, Clause Libraries, Templates, Clause Hunt baskets, and more

  • Typically assigned to Groups, not individuals

Organizations of users, primarily used to apply access rules consistently.

  • Represent teams or departments

  • Used by Access bundles to grant permissions at scale

  • Can optionally have their own Clause Library

Why this matters: Access bundles define rules, while Groups define who those rules apply to.


2. User management and identity

Manage people, accounts, and authentication safely.

These settings control who exists in the system and how they sign in.

Used to create and manage individual user accounts.

  • Add new users

  • Assign curator status

  • Enable or disable users (users can't be deleted)

  • Apply Profiles and Groups

Allows secure account switching without sharing login credentials.

  • Used to grant access to the admin account

  • Common for admin coverage or temporary handover

  • Supports impersonation in a controlled, auditable way


3. Permission profiles and default behavior

Standardize access and behavior as your organization grows.

This section deals with scaling user permissions, not content access.

Reusable sets of user rights.

  • Bundle permissions into roles

  • Define which tools users can view/use (e.g. Proofreading, Doc chat, etc.)

  • Define which actions they can take (e.g. create, edit, review)

  • Automatically applied to new users

  • Reduce manual configuration errors

Predefined AI instructions made available to users.

  • Standardize common drafting or review actions

  • Can be limited via Profiles

  • Help ensure consistency without forcing workflows

Why Prompts live here: Prompts don’t change AI models themselves; they shape how users interact with AI, which is tied to user roles and rights.


4. Content structure and outputs

Control how knowledge is classified and how results are delivered.

These tools affect how content is organized and shared, not who can access it.

Tags and filters used across structured content.

  • Applied to clauses and templates

  • Enable searching, filtering, and reporting

  • Can be managed by admins or delegated to trusted users

Controls the format of exported results.

  • Apply company branding to summaries and Playbook outputs

  • Useful for external sharing or reporting

  • Optional for organizations with strict house styles

Controls formatting behavior when inserting content.

  • Mostly unnecessary due to automatic style detection

  • Only relevant for highly standardized document environments

Did this answer your question?