Read-Only Access to a Single Environment in Liongard

Sometimes you need to give a client or third party visibility into their environment without exposing other clients or allowing changes to be made across your platform.

Read-only access lets you safely share data for audits, security reviews, or internal reporting, while keeping your Liongard instance secure.

---

What Read-Only Access Allows

With read-only access, you can let a user:

• View agents, inspectors, environments, and configuration data
• Access reports and metrics
• Create, edit, and export reports

---

Common Use Cases

You might provide read-only access when:

• A client or stakeholder needs data for an audit
• A compliance review requires validation of security controls
• A client’s internal IT or security team needs to review configurations and reports

---

Step 1: Confirm Access and User Information

Before you begin, make sure you have:

• Admin access to Liongard
• The correct environment or environment group created
• The user’s basic details (name, email, department)

If you enforce MFA, ensure it is enabled for this user.

---

Step 2: Go to Access Management

1. Navigate to Admin > Access Management
2. Click Add User

---

Step 3: Add the User’s Details

Enter the following:

• First name and last name
• Username and email
• Department (for example, Client or Audit)

Optional:

• Enable technical update emails if needed
• Turn on MFA if required by your policy

---

Step 4: Assign Read-Only Permissions

Under Roles, select:

• Reader (Configurable Scope)

This ensures the user has read-only access.

---

Step 5: Scope Their Access

Limit what the user can see by assigning:

• A single environment, or
• An environment group (recommended for client-based access)

This keeps access restricted to only what you define.

---

Step 6: Save and Send the Invite

1. Click Save
2. The user will receive an email from [email protected]
3. They can activate their account and set up credentials

---

Best Practices

• Use environment groups Keep access organized when managing multiple clients

• Assign the correct department Label users clearly (for example, Client or Audit) for easy tracking

• Limit exposure Avoid granting access to environments with sensitive or unnecessary data

• Avoid global roles Never assign global permissions to external users

---

Maintain Access Over Time

• Update access when roles change
• Remove and reassign permissions as needed
• Review external users regularly (recommended: quarterly)
• Confirm each user still requires access and has the correct scope

---

Audience

This guide is for:

• Service Desk Managers
• Security Analysts
• System Administrators who are responsible for managing user access controls and permissions in Liongard.