-
Deployment
-
Administrative Guide
- Settings
- Sharing Files
- Authentication Mechanisms
- Audit
- Backup & Restore
- Search Files using Index Service
- SSO Configuration For AdminConsole
- Admin Roles
- Access Restriction with IP Address
- System Requirements
-
- AWS S3 Storage Configuration using Access and Secret keys
- AWS S3 Storage Configuration using IAM role
- Google Storage Configuration using JSON Authentication Key
- Azure Blob/File Storage Configuration using Access Keys
- Backblaze B2 Storage Configuration using Access and Secret Keys
- DigitalOcean Storage Configuration using Access and Secret Keys
- Oracle Storage Configuration using Access and Secret Keys
- Wasabi Storage Configuration
-
- Articles coming soon
-
Tutorials
- Quick Start
- AWS S3 File Sharing With Password Protection
- Google Cloud Storage Integration
- SSO for Admin Console using IAM Identity Center
- SSL and Load balancer for NirvaShare on AWS
- SSO for AdminConsole using Azure ActiveDirectory
- SSL Using Nginx Proxy Manager
- How to Share and Manage File Access from AWS S3, Azure Blob with Salesforce Users
- Configure SSO for Admin Console using Google Workspace as Identity Provider
- Share Azure Blob Files with ActiveDirectory Users using SSO
- S3 File Sharing with Okta Users
-
Troubleshoot
Audit
Audit tracks user actions such as login, logout, file download, etc, this in turn helps organization to trace forensic or usage analytics on the user data which is vital for compliance.
Each of audit events can be enabled or disabled independently depending on the compliance requirements of the organization.

Configuration
Audit events can be selectively enabled or disabled for Admin Console and User Application. Events related to admin and delegated admin users are tracked as part of Admin Console Audits. End user events are tracked as part of User Application Audits. Only those audit events that are enabled are tracked and data will be persisted in database.

Please note that, system will generate one record in database for each audit event that is enabled. Hence enable only those which is required for your organization, otherwise lots of data may get generated over a period of time.
Reports
Audit data that gets generated based on enabled events can be queried to generate required reports with filter criteria. The filter criteria includes, event type, date range, etc. You can also search based on username. For example, you can provide a date range and query all events that happened on particular day or time or just enter a username in the search box to get all events based on on a username.
The generated search result can be can be downloadable as PDF or CSV file.

To get more information on the audit record, click on expand icon. Each of audit record event has information such as username, source IP address, time, nature of event, etc.