Glyue User Docs
  • What is Glyue?
  • Tutorials
    • Start Here
    • Building a Single-Step Integration
      • 1. Creating the Integration
      • 2. Calling the External System
      • 3. Running the Integration
      • 4. Crafting the Output
    • Building a Multi-System Integration
      • 1. Connecting to the Core
      • 2. Field Mapping
      • 3. Running the Integration
    • Building an Event-Driven Integration
      • 1. Setting up the Mock CRM
      • 2. Receiving Inbound Requests
      • 3. Triggering the Integration from the CRM
    • Building an Email Integration
      • 1. Create and Configure the Integration
      • 2. Input Validation
      • 3. Get Story IDs from Hacker News
      • 4. Get Story Content
      • 5. Sending the Email
      • 6. Wrapping Up
      • 7. Extra credit
        • extra_credit.json
    • Building a RESTful CRUD Web Service
      • 1. Integration Setup
      • 2. Vault Setup
      • 3. Create Web Service Endpoints
      • 4. Execute Web Service Endpoints with Vault Methods
      • 5. Vault Code Examples and Explanation
    • Building a Retrieval API against FIS CodeConnect
      • 1. Integration Setup
      • 2. Service Request Setup
      • 3. Field Mapping Setup
      • 4. Integration and Service Request Hook Setup
      • 5. Testing the Integration
      • 6. Common Errors
    • What is Pre-Mapping?
      • Before you start
      • Bookmarks
      • Source and Targets
      • Field Mapping Status
      • Field Mapping Comments
      • Summary
  • How-To Guides
    • How to Run an Integration from Glyue
    • How to Invite New Users
    • How to Create a Value Mapping Set
    • How to Build and Deploy a Custom Frontend
    • How to Migrate an Integration
    • How to Set Up Single Sign On (SSO)
      • Glyue Setup
      • JumpCloud Setup
      • Azure Setup
      • Okta Setup
      • Glyue SAML Config Reference
    • How to Install the Glyue App for Zoom Contact Center
    • How to use the Vault
  • Reference
    • Integration Builder Page
    • Integration Anatomy
    • Integration Components
      • Integration
      • Service Request
      • Field Mapping
      • Value Mapping Set
      • Value Mapping
      • Validation Rule
      • Mask
      • Integration Config
      • Integration Engine Versions
    • Integration Lifecycle
    • Special Functions
      • add_run_label
      • callint
      • debug
      • end
      • get_namespace
      • humanize
      • import_helper
      • keep
      • list_files
      • map_value
      • open_glyuefile
      • open_vault
      • Data Manipulation Utilities
      • calladapter
    • Special Variables
      • __adapter_config__
      • input
      • parentint
      • retvalue
      • run_history_id
      • Iterables
        • fitem/fidx
        • sritem/sridx
        • vritem/vridx/vrmsg
    • Adapters
      • Generic HTTP Adapter
      • Email SMTP Adapter
    • Web Service Endpoints
    • Vault Reference
  • Glyue Platform Reference
    • Banking Core Connectivity Guide
    • Authentication
    • Permissions
      • Service Accounts
      • Organizations
    • Frontends
    • Idempotency Layer
    • Integration Scheduler
    • Governance Reports
    • Arbitrary Integration Request Content Support
    • Admin Components
    • Logging
  • ETL
    • Glyue ETL Overview
    • Data Connectors
    • Workflows
    • Run History
    • Scheduler
Powered by GitBook
On this page
  • User / Service Account Access Report
  • Permission Log

Was this helpful?

  1. Glyue Platform Reference

Governance Reports

PreviousIntegration SchedulerNextArbitrary Integration Request Content Support

Last updated 8 months ago

Was this helpful?

Glyue provides governance reports that details the state of across all users. The report provides two views:

  • Access Report shows a list of all currently active permissions for all active users in the system.

  • Permission Log shows a ledger of all permission changes for the selected timespan. This includes both permission grants and revocations.

The meaning of each column in the report is detailed below:

User / Service Account Access Report

Column
Meaning

User

The username of the user that the permission belongs to

Organization

The organization (if any) the user belongs to

Integration

The name of the integration

Granted by

The username of the user who granted the integration permission

Granted on

The date and time (UTC) of the permission change

Permission Type

Whether the permission was granted on an individual basis (user) or via the user's membership in a group (group)

Group

If the permission was granted via a group, the name of the group that had its permissions changed

Permission Log

Column
Meaning

User

The username of the user that the permission change occured to

Name

The name of the integration or group

Action

  • grant — the user was granted the permission

  • revoke — the user's permission to the integration was revoked

  • added — the user was added to the group

  • removed — the user was removed from the group

Type

  • IntegrationPermission — the change occurred to the user's individual access to the integration

  • GroupIntegrationPermission — the change occurred because the group the user is a part of had its permission granted/revoked

  • Group — the change occured to a user's membership in a group

Time

The date and time (UTC) of the change

integration execution permissions