BF BF Technology Solutions

Avigilon Alta Access Support Intelligence Center

A problem-based support resource for mobile credentials, key cards and fobs, users, access levels, doors, readers, controllers, activity logs, connected hardware, and the Alta Access portal.

Step 01 Identify Select the affected user, credential, or entry
Step 02 Document Capture the exact event, time, and location
Step 03 Test Follow the focused troubleshooting path
Step 04 Resolve Confirm access or escalate safely
1

What problem is the client reporting?

Choose the statement that most closely matches the client’s issue.

Mobile Access
▯

Phone Will Not Open the Door

The user has Alta Open, but the assigned mobile credential does not unlock the expected entry.

#alta-mobileTroubleshoot Mobile Access
Physical Credential
◆

Card or Fob Is Denied

The credential is presented at the reader, but the user does not receive access.

#alta-fobsTroubleshoot the Credential
Entry Control
▥

Door Will Not Unlock

An access grant or unlock command is recorded, but the physical door does not change state.

#alta-doorsCheck Entry Status
User Management
●

User Is Missing Access

The user exists but does not have the expected site, zone, entry, credential, or access level.

#alta-usersReview the User
Device Status
!

Reader or Controller Is Offline

The device dashboard reports a controller, reader, or connected entry as unavailable.

#alta-hardwareCheck Hardware Status
Alta Portal
▦

Portal Controls Are Missing

Sections, sites, zones, buttons, or other interface elements are missing or do not respond.

#alta-ui-supportTroubleshoot the Portal
2

User & Invitation Support

Use for missing users, invitations, activation, suspended access, and incorrect assignments.

● User cannot access Alta Open Invitation, activation, or account-status issue

Ask the client

“What exact message appears, and was the invitation completed?”

Expected result

The user signs in and sees the assigned organization and credential.

Likely areas

User record, invitation, organization, credential, or account status.

Support checklist

  1. Confirm the email address the client is using.
  2. Verify the user exists in the correct Alta Access organization.
  3. Review the user’s activation and account status.
  4. Confirm the expected credential is assigned.
  5. Confirm access to the intended site, zone, or entry.
  6. Record the exact error before resending an invitation.
Escalate when: The account cannot be activated, several users cannot sign in, or organization-level administration is required.
✉ Invitation was not received The activation or welcome message cannot be located

Support checklist

  1. Confirm the email address on the user record.
  2. Ask the client to check junk, quarantine, and focused inbox locations.
  3. Review the current invitation or activation status.
  4. Verify the user belongs to the intended organization.
  5. Resend only after confirming the address and existing status.
  6. Document repeated delivery failures before escalation.
3

Mobile Credential Support

Use for missing mobile credentials, failed entry attempts, phone settings, or Alta Open app behavior.

▯ Mobile credential will not open an entry The user is signed in but access is not granted

Ask the client

“Does the credential appear, and what happens at the reader?”

Expected result

The active credential appears and the authorized entry responds.

Likely areas

Credential, user, permissions, access level, schedule, or entry.

Support checklist

  1. Confirm the credential appears in the Alta Open app.
  2. Verify the user and credential are active.
  3. Confirm Bluetooth is enabled.
  4. Review mobile permissions used by the client’s configuration.
  5. Confirm the correct access level and schedule.
  6. Check the activity log for the exact entry and time.
  7. Test another authorized credential at the same entry.
Interpretation: If another credential works, focus on the user, credential, phone, and access assignment. If none work, investigate the entry, reader, controller, schedule, or connected hardware.
⌕ Credential is missing from the app The user signs in but cannot see the credential

Support checklist

  1. Confirm the correct Alta Access organization.
  2. Verify an active mobile credential is assigned.
  3. Confirm invitation and activation completion.
  4. Review site and access-level assignments.
  5. Record the app version and phone platform.
  6. Restart the app after documenting the current state.
4

Cards, Key Fobs & Physical Credentials

Use for denied credentials, replacements, lost credentials, and assignment problems.

◆ Card or fob does not unlock the door The reader denies access or does not respond

Ask the client

“Does the reader react, and does the credential work elsewhere?”

Expected result

The reader detects the active credential and unlocks the authorized entry.

Likely areas

Credential status, user, access level, schedule, entry, or reader.

Support checklist

  1. Confirm the credential is assigned to the correct user.
  2. Verify the credential is active and not expired.
  3. Confirm the correct access level and schedule.
  4. Review the activity log for the exact entry and time.
  5. Test the credential at another authorized entry.
  6. Test a known-working credential at the affected entry.
  7. Document reader response or lack of response.
×

Lost Credential

  • Confirm the user and credential
  • Disable the lost credential
  • Document the reported loss
  • Issue an approved replacement
  • Test the replacement
+

Replacement Credential

  • Confirm the user record
  • Record the old identifier
  • Assign the new credential
  • Confirm access assignments
  • Disable the old credential
5

Doors, Entries & Reader Support

Use for state problems, failed unlocks, denied access, and reader behavior.

▥ Entry does not lock or unlock as expected Schedule, relay, ACU, wiring, lock, or power issue

Ask the client

“Does the dashboard state match the physical door state?”

Expected result

The dashboard and physical lock state match the approved schedule.

Likely areas

Schedule, relay, controller, wiring, lock hardware, power, or firmware.

Portal and configuration checks

  1. Record the entry, time, physical state, and dashboard state.
  2. Check activity logs for grants, denials, and commands.
  3. Review the assigned entry schedule and events.
  4. Check for important firmware updates.
  5. Confirm the configured relay corresponds to the door lock.
  6. Issue a controlled test and document both responses.
Escalate to a trained integrator when: The dashboard and physical state differ, the correct relay is configured but the lock does not respond, or physical inspection is required.
! Reader shows denied access The reader responds but access is not authorized

Support checklist

  1. Record the user, credential, entry, date, and time.
  2. Locate the corresponding activity event.
  3. Confirm the credential is active.
  4. Review the access level and schedule.
  5. Confirm the entry belongs to the intended site or zone.
  6. Check expiration and temporary restrictions.
6

Access Levels, Sites & Schedules

Use when access works in the wrong place, at the wrong time, or not at all.

✓

Authorized Area Is Denied

  • Confirm user and credential
  • Review access levels
  • Confirm site, zone, and entry
  • Review schedule
  • Check expiration
  • Review activity logs
!

User Has Too Much Access

  • Review assigned access levels
  • Check group assignments
  • Review temporary access
  • Confirm schedule scope
  • Document all changes
⌚

Schedule Is Incorrect

  • Confirm expected days and times
  • Review entry schedules
  • Review access-level schedules
  • Check holidays and exceptions
  • Confirm site time zone
7

Activity Logs & Incident Review

Establish what Alta Access recorded before changing credentials, schedules, entries, or hardware settings.

▤

Collect These Details

  • User or credential identity
  • Entry or reader name
  • Exact date and time
  • Grant, denial, or command
  • Dashboard state
  • Physical door response
⌕

Review for Patterns

  • Repeated denials
  • Door forced open
  • Door held open
  • Manual unlock commands
  • Offline devices
  • Events after recent changes
8

Controllers, Readers & Connected Hardware

Use for device alerts, offline controllers, reader communication, door contacts, and lock-output concerns.

▦ Controller or Smart Reader is offline The device dashboard reports a communication issue

First-line support checklist

  1. Record the device and last reported status.
  2. Determine whether one or several devices are affected.
  3. Review dashboard alerts and diagnostics.
  4. Check for important firmware updates.
  5. Use the approved dashboard restart option when appropriate.
  6. Document whether the device and connected entries recover.
  7. Escalate unresolved physical, power, network, or wiring issues.
Safety requirement: Disconnect power before servicing. Controller, wiring, relay, lock, and power-supply work must be completed by qualified personnel.
9

Client Support Scripts

Use these copy-ready responses for consistent client support.

Opening the Request

Thank you for contacting BF Technology Solutions. Please provide the user name, credential type, affected door, and exact time the issue occurred.

Requesting an Access Test

Please present the credential once at the affected reader and tell me exactly how the reader responds. Please avoid repeated attempts until the first event is reviewed.

Requesting a Screenshot

Please send a screenshot of the message shown in Alta Open. Do not include passwords, activation links, or confidential information.

Explaining Hardware Escalation

We completed the user, credential, schedule, dashboard, and activity log checks. The remaining issue may require a qualified technician to review the controller, relay, wiring, lock, or power supply.
10

Alta Open Mobile Client Guide

Share the BF Technology Solutions quick guide with clients who need installation, mobile access, notification, or phone-setting support.

BF Technology Solutions Client Resource

Avigilon Alta Open Mobile App Setup Guide

This client-facing reference provides setup guidance for iPhone and Android users, including mobile unlock preparation, notifications, hands-free access settings, and first-line troubleshooting.

  • Alta Open installation
  • iPhone settings
  • Android settings
  • Bluetooth preparation
  • Location permissions
  • Notification settings
  • Hands-free access
  • Client troubleshooting
Open Mobile Credential Guide PASTE-SQUARESPACE-PDF-URL-HERE Download Client Guide #alta-mobile Mobile Troubleshooting
Publishing note: Upload the PDF to Squarespace and replace both PDF placeholders with the generated Squarespace file URL.
PASTE-SQUARESPACE-PDF-URL-HERE
Alta Open Mobile App Guide Select to open the BF Technology Solutions setup, notification, and troubleshooting guide.
11

Alta Access Portal & UI Troubleshooting

Use when pages have broken layouts, missing sections, unavailable controls, or non-responsive buttons.

▦ Portal layout is broken or controls are missing Missing access sections, sites, zones, buttons, or page elements

Ask the client

“Does this affect one browser or multiple users and devices?”

Expected result

The portal displays the expected controls, sections, sites, and zones.

Likely areas

Zoom, resolution, cache, browser extensions, browser, device, or service.

1. Check display and zoom Use the recommended display resolution and reset browser zoom to 100%.
2. Clear cached browser data Clear cached files and cookies, then restart the browser.
3. Test another environment Try another browser, a private window, another device, or another network.
4. Review browser extensions Temporarily disable extensions that may interfere with rendering, following the client’s security policy.
Collect before escalation: Screenshot or recording, browser and device, organization name, organization ID, and whether one or multiple users are affected.
12

Official Avigilon Alta Resources

Use these sources for current documentation, troubleshooting, community resources, and manufacturer support.

Official Knowledge Article
▦

Troubleshooting UI Issues in Alta Access

Guidance for missing interface elements, broken layouts, non-responsive buttons, browser testing, and escalation evidence.

Open UI Troubleshooting
Official Support Center
?

Avigilon Alta Support

Access manufacturer knowledge articles, discussions, technical support options, and online case submission.

Visit Alta Support
BF Technology Solutions
BF

Mobile Credential Client Guide

Open the BF Technology Solutions guide for Alta Open installation, mobile settings, notifications, and first-line troubleshooting.

PASTE-SQUARESPACE-PDF-URL-HERE Open Client Guide
Resource priority: Start with this BF Technology Solutions knowledge center for first-line client support. Use official Avigilon resources for current manufacturer guidance, known issues, and specialized escalation.
13

Open an Alta Access Support Ticket

Collect this information so the next technician or manufacturer can continue without repeating completed troubleshooting.

Required ticket information

Customer Company and primary contact
Site Building, floor, suite, and location
User Name and Alta Access email
Credential Mobile, card, fob, or other type
Entry Door, reader, zone, and site
Device Reader, controller, ACU, and identifier
Event Time Date, time, and time zone
Activity Result Grant, denial, command, or no event
Dashboard State Online status and reported lock state
Physical State Actual door and lock behavior
Recent Changes User, schedule, firmware, network, or hardware
Tests Completed Every completed step and result
/support-request Request Alta Access Support

BF Technology Solutions

Your Partner in Technology for Avigilon Alta Access, mobile credentials, secure entries, readers, controllers, managed IT, network infrastructure, and connected workplace security.

This knowledge center is a first-line troubleshooting reference. Credentials, access levels, schedules, relays, controllers, powered locks, wiring, and security settings should be changed only by authorized personnel under approved security and change-control procedures.