Account changes, traced back by action.
Review events such as account creation, member invitations, and role changes or removals. Each record shows the action, object type, and time of occurrence, making it easy to trace changes in team management.
Taking over a team. Start with the management history.
Trace member changes, Relay creation requests, node service entitlements and bring-your-own-proxy takeover records to understand the origins and service periods of existing resources.
View record scopeMember changes, resource requests. Each has its own record.
Relay requests, view the creation history.
Review creation requests along with their status, associated resources, and creation time to understand how a connection was established. Request status and the node's actual connection status are viewed separately.
Ingress and egress, service periods available.
Gateway service entitlements.
Trace the product, associated instance, service period, and status of ingress resources, and view the onboarding records for bring-your-own ingress.
Connector service entitlements.
Review the product, associated instance, service period, and status of egress resources to understand the resource history of managed or bring-your-own egress.
BYOP onboarding records.
Separately review the resources, onboarding time, and status of bring-your-own SOCKS5 proxies connected to AXVIA. The proxy service and the provider's network remain the customer's responsibility.
Management history, viewed according to permissions.
Team owners and administrators can view account audits. Users can view resources and use connection configurations, but audit read access is not granted to them.
Learn about destination access auditing →Frequently asked questions.
Can regular users view all account operations?
No. Account audit requires audit read permission, which owners and administrators have but the user role does not. Resource read permission is not the same as audit read permission.
Does the operation audit show business access targets?
This section shows the management history of teams and resources. Business target domains or IPs, protocols, traffic and connection counts are viewed in the access audit of the final Connector.
Does a completed creation request mean the device is already connected?
Request records are used to review the creation process and status. Whether a node is ready, whether the configuration has been applied and whether the device is connected must still be checked in the corresponding node, Relay and terminal details. Historical request records cannot replace live status.