As a hybrid workplace AV and collaboration tech admin supporting our corporate live event and video production workflows, Avaza’s neatly organized profile panel paired with its built-in notification, preference and security controls keeps our field tech crew aligned, and its integrated timesheet and resource scheduling functionality saves me roughly three hours each week reconciling on-location event labor and hardware prep work. I manage multi-camera webinars, conference room AI camera deployments, streaming tests and remote troubleshooting shifts, so every task is tied to client event windows, and accurate, traceable logging matters both for billing and our meeting-recording privacy compliance requirements.

The My Profile modal is where every member of my AV team sets up their baseline identity settings before they jump onto event work. I really appreciate the split tab layout separating Profile, Preferences, Notifications and Security. The initials field is a small detail that delivers consistent value; when a tech is out on-site setting up HDMI switchers or testing Camera-M auto-tracking, their initials pop up on task cards and schedule views even without uploading a profile photo. During our quarterly all-hands live stream last month, we had four technicians spread across two office locations, and I could instantly see who was assigned to encoder setup, camera calibration, Q&A moderation and post-recording archiving without digging through separate spreadsheets.

The Notifications tab is my go-to for tuning alert behavior for our crew. Our events often run outside standard business hours, so individual team members can toggle off non-urgent alerts overnight while keeping critical triggers like last-minute client scope changes or streaming failure alerts active. The dedicated Security tab is equally important, since our project records contain meeting recording schedules, conference room locations and access notes that fall under our corporate privacy policy. It gives every technician a dedicated spot to review login activity and reset credentials, so I don’t get flooded with password-reset tickets in the middle of a live production.

One unexpected benefit I’ve discovered is how profile position title data flows into Avaza’s reporting engine. Once a technician fills in their role, such as live-stream engineer or conference-room AV installer, I can filter timesheet and utilization reports by specialty. This makes it easy to prove how much billable engineering time we allocate to AI camera rollouts versus standard room hardware installs. It also helps me flag overloaded team members before a busy event week, so I can rebalance our on-site schedules and avoid burnout during peak webinar seasons. The left-hand navigation linking Projects, Tasks, Team Schedule and Expenses creates a tight workflow; once a tech finalizes their profile, they can log setup hours, submit cable or adapter expenses and reference event checklists all in one platform.

Suggestions: Add native integration with streaming and AV test platforms to auto-log event uptime and camera health data against tasks; build custom compliance profile fields to flag which technicians have completed meeting-recording privacy training; expand security audit trails to log profile edits and setting changes for our corporate data governance reviews. Review collected by and hosted on G2.com.

As a hybrid workplace AV and collaboration tech admin running corporate live streams and conference-room camera deployments, the biggest pain point with Avaza is its limited custom profile field set and shallow user-change audit trail, which creates real compliance friction for our meeting-recording governance workflows. I track which technicians have completed our video privacy training, which events allow recording, and which rooms have active AI auto-tracking cameras, but the native profile form only includes basic fields like name, phone, title and initials. There’s no built-in way to add mandatory flags for privacy training status, camera access clearance, or event recording authorization. Last month, we ran a company-wide all-hands webinar, and I had to cross-reference Avaza’s schedule against a separate spreadsheet of trained staff. It took nearly two hours just to confirm every tech on shift understood our corporate recording rules, and I had no way to filter Avaza reports to only show cleared team members.

I’m also frustrated that the activity log does not capture profile edits and preference changes at the user level. Our profile panel lets technicians update their contact details, notification rules and security settings independently, but there is no timestamped record showing who edited what and when. If a team member modifies their notification settings to suppress critical stream-failure alerts before a live event, I have no way to trace that change after the fact. For our internal privacy audits, we need proof that user access settings haven’t been altered without oversight, and this gap forces me to keep redundant offline logs, adding extra admin work every audit cycle.

Another major shortfall is the lack of native integration with AV test, streaming and camera platforms like Camera-M. Right now, all our camera uptime logs, USB/HDMI compatibility test results and AI framing stability data live in separate tools. When a tech logs hours for a camera calibration job in Avaza, there’s no automatic pull of that session’s test metrics into the task record. If we have a client inquiry about a stream dropout during a virtual event, I have to jump between three different systems to match the Avaza timesheet entry to the camera error logs. This slows down incident reviews and makes it harder to tie billing directly to verified equipment performance.

The notification controls in the profile panel also lack granular scheduling logic. Our events often run after standard business hours, but the notification toggle is all-or-nothing per alert type. I cannot set rules to suppress non-urgent alerts overnight while retaining high-priority stream-down notifications only during scheduled event windows. Several weeks ago, one of our night-shift stream engineers missed a critical encoder fault alert because they’d turned off all project notifications to avoid off-hours spam.

Suggestions: Add fully customizable mandatory profile fields for AV compliance, including privacy training expiry and camera access permissions; expand the activity audit log to log every profile, notification and security-setting edit with user attribution and timestamps; build webhook triggers to pull camera health, streaming uptime and AI tracking test data from our AV platforms directly into linked Avaza tasks; add time-based notification rules so alerts only fire during assigned event windows. Review collected by and hosted on G2.com.