1. Getting Started

Account Setup Guide

This guide walks you through creating your Alingo account, setting up your organization, and inviting your team. Prerequisites Before you begin, ensure you have: - A valid email address - Administrative access (if joining an existing organization) - Google Workspace account (optional, for Google Drive integration) Creating Your Account Step 1: Registration 1. Navigate to the Alingo registration page 2. Click "Register" or "Sign Up" 3. Provide the following information: - Full Name - Your first and last name - Email Address - Your work email - Password - Strong password (minimum 8 characters) 1. Accept the Terms of Service and Privacy Policy 2. Click "Create Account" [SCREENSHOT: Registration form showing name, email, and password fields] Step 2: Email Verification 1. Check your email inbox for a verification message from Alingo 2. Click the verification link in the email 3. You'll be redirected to the login page 4. Sign in with your credentials Note: If you don't receive the email within 5 minutes, check your spam folder or request a new verification email. Creating Your Organization When you first log in, you'll be prompted to either create a new organization or join an existing one. Option A: Create a New Organization If you're the first person from your company: 1. Click "Create New Organization" 2. Enter your Organization Name (e.g., "Acme Corporation Legal") 3. Optionally add a Display Name (how it appears to users) 4. Optionally add your Domain (e.g., "acme.com") for automatic user verification 5. Click "Create Organization" [SCREENSHOT: Organization creation form] You'll automatically be assigned the Owner role with full administrative privileges. Option B: Join an Existing Organization If your organization already exists: 1. Click "Join Existing Organization" 2. Enter your organization's domain or invite code 3. Click "Request Access" 4. Wait for an administrator to approve your request You'll receive an email when your access is granted. Understanding User Roles Alingo has two types of roles: Organization Roles (Administrative) These control administrative access: - Owner - Full control, can delete organization, manage billing - Admin - Can manage users, settings, and integrations - Member - Standard user access Functional Roles (Feature Access) These determine what features you can access: - Admin - Full platform access, can manage all features - Legal - Access to all legal tools, can create playbooks and guardrails - Business - Self-service access with guardrail boundaries Important: You can have one organization role AND one functional role. For example, you might be an "Owner" (organization role) and "Legal" (functional role). For a detailed breakdown of permissions, see Roles and Permissions. Initial Profile Setup Complete Your Profile 1. Click your avatar in the top-right corner 2. Select "Settings" 3. Navigate to the "Profile" tab 4. Complete your information: - Full Name - Job Title - Department - Phone Number (optional) 1. Click "Save Changes" [SCREENSHOT: Profile settings page] Configure Notification Preferences 1. In Settings, go to "Profile" tab 2. Scroll to "Notification Preferences" 3. Choose your preferences: - Email notifications (on/off) - In-app notifications (on/off) - Specific notification types 1. Click "Save Changes" Set Your Language 1. In Settings, go to "Language" tab 2. Select your preferred language from the dropdown 3. The interface will update immediately [SCREENSHOT: Language selector] Inviting Your Team Once your organization is set up, invite team members: Step 1: Access User Management 1. Go to Settings (top-right avatar menu) 2. Click the "Users" tab 3. Click "Invite User" [SCREENSHOT: User management interface with invite button] Step 2: Send Invitations 1. Enter the user's email address 2. Enter their full name 3. Select their functional role (Admin, Legal, or Business) 4. Select their organisation role (Owner, Admin, or Member) 5. Click "Send Invitation" [SCREENSHOT: User invitation dialog] The invited user will receive an email with instructions to create their account. Step 3: Manage Pending Invitations You can track invitation status in the Users tab: - Pending - Invitation sent but not accepted - Active - User has accepted and is using the platform - Inactive - User account has been deactivated Recommended Next Steps After account setup, we recommend: 1. Complete the Quick Start - Upload your first document and ask a question (5 minutes) 2. Set up integrations - Connect Google Drive for seamless document sync 3. Create your first Playbook - Build a standardized clause library 4. Configure Guardrails - Set boundaries for self-service Troubleshooting Can't verify email? - Check your spam/junk folder - Ensure you clicked the most recent verification link - Request a new verification email from the login page Organization already exists? - Contact your organization's Owner or Admin for an invitation - If you believe you should be the owner, contact Alingo support Forgot password? 1. Click "Forgot Password" on the login page 2. Enter your email address 3. Check your email for reset instructions 4. Create a new password Can't invite users? - Ensure you have Owner or Admin organisation role - Check that the email address is correct - Verify the user isn't already in your organisation Security Best Practices - Use a strong password - Mix of uppercase, lowercase, numbers, and symbols - Enable two-factor authentication - Always enable 2FA - Don't share credentials - Each user should have their own account - Review user access regularly - Remove access for departed team members - Use organisation domain - This helps with automatic user verification Next Steps: - Quick start guide → - Understand roles and permissions → - Upload your first documents →

Alingo Platform Overview

Welcome to Alingo—the AI co-pilot for corporate legal teams. Scale your legal capacity without adding headcount. What is Alingo? Alingo is the first AI co-pilot that helps corporate legal teams scale their output without adding staff or changing where you work. Contract redlining that thinks like you, legal answers for business teams that sound like you. Alingo handles 80% of the work. You handle 100% of the decisions. Who is Alingo For? For Legal Teams Corporate legal teams use Alingo to scale capacity while maintaining complete control: - Intelligent contract review - AI analyzes and redlines contracts in Google Docs against your policies - Risk highlighting - Instantly identify terms that require legal attention - Policy-aligned redlines - Get suggestions that comply with your legal guidelines - Clause explanations - Understand complex legal language with plain-English explanations - Playbook support - Apply your organization's legal standards consistently across all contracts Result: 40+ hours of legal time saved monthly. Focus on strategic legal counsel, not routine work. For Business Teams Sales, Procurement, and HR teams get instant answers without waiting for legal: - Instant legal answers - Get guidance in Slack based on your established positions - Self-service contracts - Handle standard agreements independently using approved Playbooks - Clear guardrails - Know exactly when Legal involvement is needed - Seamless workflow - Works in tools you already use (Slack, Google Docs, Jira) Result: 70% reduction in routine legal questions. Move deals forward without bottlenecks. Core Capabilities 1. Docs Monitor all contracts in one dashboard: - Track status from draft to execution - Filter by department or risk level - Identify bottlenecks instantly - Complete visibility with minimal effort 2. Playbooks Your organization's legal standards, consistently applied: - Automatically infer legal guidelines from your existing contracts - Pre-approved language for common scenarios - Alternative clauses and fallback positions - Marketplace of ready-to-use templates 3. Escalations AI escalates complex matters to you with full context: - Automatic routing based on risk level - Complete context provided for every escalation - Focus on strategic legal work - Never miss critical issues 4. Stats Quantify your legal impact: - Metrics on time saved, deal velocity, and cost reduction - Track adoption rates and monitor trends - Generate ROI reports for executive presentations - Demonstrate legal team value 5. Guardrails Empower business teams while maintaining compliance: - Set clear boundaries for what business users can approve - Define non-negotiable terms and escalation triggers - Enable safe self-service without becoming a bottleneck - Full control over contract workflows 6. Chrome Extension Real-time contract analysis in Google Docs: - Policy-aligned redlines while you review - Risk highlighting with severity levels - One-click suggestions with explanations - Comments added automatically Key Benefits Scale Without Headcount - 40+ hours of legal time saved monthly - 70% reduction in routine legal questions - Handle twice the contract volume with the same team - Reduce outside counsel spend Complete Control - You define legal standards and risk tolerance - AI applies your guidelines consistently - Strategic decisions stay with your expertise - Full audit trail of all actions Seamless Integration - Works where you already work—no new platforms to learn - Google Docs, Slack, Google Drive, Jira - Real-time collaboration between Legal and Business - Clear escalation paths with full context How It Works Alingo brings AI assistance to where you already work: 1. Set your playbooks - Define your legal standards and risk tolerance once 2. AI applies consistently - Every contract reviewed against your guidelines 3. Get policy-aligned suggestions - Redlines that comply with your policies 4. Review and decide - You handle 100% of the decisions 5. Always learning - Improves as you add more contracts and feedback All while keeping your data secure, private, and under your control. Getting Started Ready to transform your legal workflow? Here's your path: 1. Create your account - Set up your organisation 2. Quick start guide - Get value in 5 minutes 3. System requirements - Ensure compatibility 4. Understand roles - Learn about permissions Who Benefits from Alingo? - Head of Legal - Scale your team without adding headcount. Reduce outside counsel spend while maintaining full control - In-house Counsel | Eliminate repetitive contract reviews. Focus on strategic work while Alingo handles routine matters - Sales Teams | Get immediate answers to contract questions. Move deals forward without waiting for legal review - Procurement | Speed up vendor agreements with instant access to your company's standard negotiation positions Support Need help? We're here for you: - Documentation - Comprehensive guides in this helpdesk - In-app support - Click the chat widget in the bottom-right - Contact us - Visit alingo.ai/contact Next Steps: - Set up your account → - Quick start guide → - Explore features -

User Roles and Permissions

Understanding roles and permissions in Alingo helps you configure appropriate access for your team members and maintain security while enabling collaboration. Overview Alingo uses a dual-role system: 1. Organization Roles - Control administrative access 2. Functional Roles - Determine feature access Every user has BOTH an organisation role AND a functional role. Example: Jane might be an "Admin" (organisation role) with "Legal" (functional role), giving her both administrative privileges and full legal feature access. Organisation Roles These roles control administrative capabilities within your organisation. Owner Who should have this: The primary account holder, typically the General Counsel or Legal Operations lead. Capabilities: - ✅ Full administrative access - ✅ Manage all users (invite, edit, deactivate, delete) - ✅ Delete organisation - ✅ Manage billing and subscription - ✅ Configure all integrations - ✅ Access audit logs - ✅ Modify organisation settings - ✅ All permissions of Admin + Member roles Restrictions: - ❌ Cannot be removed by other admins - ❌ Organisation must always have at least one owner Best Practices: - Limit to 1-2 people maximum - Use for C-suite legal leadership only - Consider succession planning Admin Who should have this: Senior legal team members who manage the platform. Capabilities: - ✅ Invite and manage users (except remove Owner) - ✅ Configure integrations - ✅ Access audit logs - ✅ Modify organisation settings - ✅ View billing information - ✅ All permissions of Member role Restrictions: - ❌ Cannot delete organisation - ❌ Cannot remove Owner - ❌ Cannot modify billing/payment methods Best Practices: - Assign to legal operations staff - Typically 2-5 people per organisation - Balance security with operational needs Member Who should have this: All other users in your organisation. Capabilities: - ✅ Use all assigned features (based on functional role) - ✅ View their own profile - ✅ Change their own notification preferences - ✅ Access shared resources (playbooks, documents) Restrictions: - ❌ Cannot invite users - ❌ Cannot modify organisation settings - ❌ Cannot access admin features - ❌ Cannot view audit logs Best Practices: - Default role for most users - Review and confirm periodically - Upgrade to Admin only when necessary Functional Roles These roles determine which features and capabilities users can access. Admin (Functional) Who should have this: Platform administrators and power users who need access to everything. Feature Access: - ✅ AI Assistant (all modes) - ✅ Document Vault (upload, manage, delete) - ✅ Playbooks (create, edit, share, delete) - ✅ Marketplace (browse, add templates) - ✅ Guardrails (create, edit, delete) - ✅ Legal Tickets (view all, create, assign) - ✅ Chrome Extension (all features) - ✅ All integrations - ✅ Advanced settings Use Cases: - Legal operations managers - Platform administrators - Power users who configure the system Legal (Functional) Who should have this: Legal professionals who create and manage legal content. Feature Access: - ✅ AI Assistant (all modes) - ✅ Document Vault (upload, manage, organize) - ✅ Playbooks (create, edit, share) - ✅ Marketplace (browse, add, fork templates) - ✅ Guardrails (create, edit - to set business boundaries) - ✅ Legal Tickets (view all, respond, resolve) - ✅ Chrome Extension (all features) - ✅ Document analysis and clause extraction - ✅ Integrations (view status, use features) Restrictions: - ❌ Cannot delete critical resources without permission - ❌ Limited admin configuration access Use Cases: - Lawyers and legal counsel - Paralegals - Legal researchers - Contract managers Business (Functional) Who should have this: Business users who need self-service legal capabilities within guardrails. Feature Access: - ✅ AI Assistant (standard and web search modes) - ✅ Document Vault (upload, view own documents) - ✅ Playbooks (view and use approved templates) - ✅ Marketplace (browse templates) - ✅ Legal Tickets (create, view own tickets) - ✅ Chrome Extension (basic features on approved documents) Restrictions: - ❌ Cannot create/edit playbooks - ❌ Cannot create/edit guardrails - ❌ Cannot use document search mode without approved documents - ❌ Cannot access other users' documents - ❌ Cannot configure integrations - ❌ Limited to guardrail-approved actions Use Cases: - Sales teams - Procurement specialists - HR professionals - Business development - Any non-legal staff needing legal resources Permission Matrix Detailed breakdown of permissions by role combination: Administrative Permissions | Permission | Owner | Admin | Member | |------------|-------|-------|--------| | Delete organisation | ✅ | ❌ | ❌ | | Manage billing | ✅ | View only | ❌ | | Invite users | ✅ | ✅ | ❌ | | Edit user roles | ✅ | ✅ (except Owner) | ❌ | | Deactivate users | ✅ | ✅ | ❌ | | Delete users | ✅ | ❌ | ❌ | | Configure integrations | ✅ | ✅ | ❌ | | Access audit logs | ✅ | ✅ | ❌ | | Modify organisation settings | ✅ | ✅ | ❌ | Feature Permissions (by Functional Role) | Feature | Admin | Legal | Business | |---------|-------|-------|----------| | AI Assistant - Standard Chat | ✅ | ✅ | ✅ | | AI Assistant - Document Search (RAG) | ✅ | ✅ | Limited* | | AI Assistant - Web Search | ✅ | ✅ | ✅ | | AI Assistant - Document Drafting | ✅ | ✅ | Templates only | | Upload Documents | ✅ | ✅ | ✅ | | View All Documents | ✅ | ✅ | Own only | | Delete Documents | ✅ | ✅ | Own only | | Create Playbooks | ✅ | ✅ | ❌ | | Edit Playbooks | ✅ | ✅ | ❌ | | View Playbooks | ✅ | ✅ | ✅ | | Use Playbook Templates | ✅ | ✅ | ✅ | | Fork Marketplace Templates | ✅ | ✅ | ❌ | | Create Guardrails | ✅ | ✅ | ❌ | | View Guardrails | ✅ | ✅ | ✅ | | Create Legal Tickets | ✅ | ✅ | ✅ | | Assign Tickets | ✅ | ✅ | ❌ | | Resolve Tickets | ✅ | ✅ | ❌ | | Chrome Extension - Full Features | ✅ | ✅ | Limited** | | Analyse Documents for Clauses | ✅ | ✅ | ❌ | | Configure Integration Settings | ✅ | View only | ❌ | - Business users can search documents within guardrail-approved scope ** Business users limited to approved document actions Role Assignment Examples Scenario 1: Small Legal Team (5 people) General Counsel - Organization Role: Owner - Functional Role: Legal - Rationale: Needs full control and legal capabilities Legal Operations Manager - Organization Role: Admin - Functional Role: Admin - Rationale: Manages the platform and users 2 Associate Counsels - Organization Role: Member - Functional Role: Legal - Rationale: Create content, don't need admin access Paralegal - Organization Role: Member - Functional Role: Legal - Rationale: Support legal team, use all features Scenario 2: Legal + Business Users (20 people) Chief Legal Officer - Organization Role: Owner - Functional Role: Legal 2 Legal Operations Specialists - Organization Role: Admin - Functional Role: Admin 3 Lawyers - Organization Role: Member - Functional Role: Legal 2 Paralegals - Organization Role: Member - Functional Role: Legal 12 Business Users (Sales, Procurement, HR) - Organization Role: Member - Functional Role: Business Changing User Roles Who Can Change Roles - Owners can change any role (except their own) - Admins can change Member and Admin roles (not Owner) - Members cannot change any roles How to Change a User's Role 1. Navigate to Settings > Users tab 2. Find the user in the list 3. Click the menu icon (⋮) next to their name 4. Select "Edit Roles" 5. Choose new Organization Role and/or Functional Role 6. Click "Save Changes" [SCREENSHOT: Edit user roles dialog] The change takes effect immediately - the user may need to refresh their browser. When to Change Roles Promote to Admin when: - User needs to manage other users - User handles integration configuration - User requires audit log access - User manages organization settings Change Functional Role when: - Job responsibilities change - User needs different feature access - User moves from Business to Legal team (or vice versa) Demote when: - User no longer needs administrative access - User changes departments - Security review recommends reduction Best Practices Principle of Least Privilege Give users only the access they need: - Start with Member + Business for new users - Upgrade to Legal when they need to create content - Reserve Admin for true administrators (2-5 people max) - Limit Owner to 1-2 people Regular Access Reviews Quarterly review process: 1. Export user list from Settings > Users 2. Review each user's roles 3. Verify roles match current job functions 4. Remove access for departed employees 5. Downgrade users who no longer need elevated access Onboarding Process New user checklist: 1. Determine appropriate functional role (Business vs Legal) 2. Assign Member organisation role by default 3. Send invitation with role clearly stated 4. Provide role-specific training 5. Review access after 30 days Offboarding Process When a user leaves: 1. Deactivate account immediately (Settings > Users > Deactivate) 2. Review and reassign their open tickets 3. Transfer ownership of critical playbooks 4. Document their contributions in audit log 5. After 90 days, consider deletion (Owner only) Security Considerations Role Separation Never combine: - Owner + Business role (inappropriate access level) - Member org role + need to manage users (promote to Admin) Always separate: - Administrative access from day-to-day business access - Legal content creation from administrative functions Audit Trail All role changes are logged: - Who made the change - When it was made - What changed (from X role to Y role) - IP address and user agent View audit logs: Settings > Audit tab Troubleshooting User can't access a feature Check: 1. Their functional role (Admin, Legal, or Business) 2. The feature requirements (see permission matrix) 3. Whether they need role upgrade 4. Organisation-wide feature flags User can't be promoted to Owner Reason: Organisation can have multiple Owners Solution: Current Owner can promote them via Settings > Users > Edit Roles Changes not taking effect Try: 1. User should refresh browser (F5 or Cmd+R) 2. Clear browser cache 3. Sign out and sign back in 4. If persists, contact support Can't find user management Check: 1. You need Owner or Admin organization role 2. Navigate to Settings (top-right menu) > Users tab 3. If still not visible, you're likely a Member (contact your admin) Related Articles: - Account setup → - User management tutorial → - Security best practices → - Audit logs →