Security across discovery and access

Voyager provides security mechanisms for authentication, authorization, roles, groups, access rules, and record visibility.

Security should be understood as a set of layers rather than a single control.

Authentication and identity

Voyager supports internal users as well as integration with external authentication environments using supported identity mechanisms.

Authenticated identities can be associated with roles, groups, and other information used in platform authorization and security configuration.

Record-level discovery controls

Voyager can use indexed security information and configurable access rules to determine which catalog records are visible to a user.

Source permissions or other security metadata may also be indexed where the applicable connector and configuration provide them. Exact fidelity depends on the source and integration.

Discovery and delivery are separate decisions

Being able to discover a catalog record is not always the same as being authorized to retrieve the underlying source content.

A deployment can apply Voyager security controls to catalog discovery while retaining a source system or external authorization service as the authoritative decision point for delivery or access to the underlying data.

External authorization services

Where required, Voyager can participate in architectures that use external systems to provide authorization or releasability information.

Those external services remain responsible for their decisions. Voyager provides the integration and workflow mechanisms needed to incorporate the result where appropriate.

Security depends on the deployment

Voyager security capabilities should not be interpreted as proof of accreditation, certification, cross-domain approval, or authorization for a specific environment.

Identity systems, network boundaries, source permissions, customer policies, infrastructure security, and external authorization services remain part of the overall solution architecture.