Skip to main content
Back to Integrations
Docusign logo

Docusign

See who can administer and send from Docusign, who holds a seat but hasn't logged in for months, which permission profiles grant account management or API sending on behalf of others, where Connect webhooks push envelope events (and whether they include the signed documents), your claimed domains and single sign-on setup, and Docusign Monitor's security event history - never envelopes, documents or recipients.

Questions you can answer 13

Each one is a saved query that ships with ConfigView, reading your Docusign data on your own server. Ask it in plain English, SQL, Slack or the API.

  • Who are the Docusign admins?
  • Who can change Docusign account settings or manage users?
  • Which Docusign permission profiles allow account management, and who has them?
  • Which apps are using the Docusign API?
  • What integration keys called Docusign in the last 30 days?
  • Where does Docusign send signed documents?
  • Which Docusign Connect webhooks go to outside hosts?
  • Is Docusign pushing completed agreements to Zapier or other third parties?
  • Which Docusign users haven't logged in for 90 days?
  • Are we paying for Docusign seats nobody uses?

What ConfigView collects from Docusign 11

  • Accounts

    Each Docusign eSignature account the connection can see: plan, plan dates, seats allowed and in use, and whether sending is blocked or the account suspended.

  • Connect Webhooks

    Docusign Connect configurations - the webhooks that push envelope events out of Docusign: destination host (never the full URL or credentials), whether completed documents are included, who and which events are covered, and how the receiver is authenticated.

  • Group Members

    Who is in each Administrators and custom group on each account. The Everyone group is skipped: it is every user, already in Users.

  • Groups

    Groups on each account - the built-in Administrators and Everyone groups and custom ones - with type, the permission profile they grant and member count.

  • Identity Providers (SSO)

    Single sign-on identity providers configured for the organization: name, protocol, issuer, whether users are created automatically on first login, and when the signing certificates expire. Login URLs are reduced to their host.

  • Monitor Audit Events

    Docusign Monitor's security event stream: logins, admin and permission changes, user changes and API activity across the organization - who, what, when, from which IP and country, and which integration key. Kept as a permanent ledger.

  • User Profiles (last login)

    Per-user profile from Docusign Admin: last login, organization admin, single sign-on (federated) status, two-step verification requirement, and every account membership with its permission profile and admin flag. Refreshed a slice per run, stalest first.

  • Organization Users

    Every user of every account in the Docusign organization, from Docusign Admin: user and membership status, when they joined and were closed, whether SCIM manages them, and their licence.

  • Permission Profiles

    Permission profiles on each account and what they allow: full account administration, sending, API access (including sending on behalf of others), bulk send and template access, with how many users hold each.

  • Claimed Domains

    Email domains the organization has claimed in Docusign Admin, whether each is verified, and which identity provider (single sign-on) it is tied to.

  • Users

    Every user on each eSignature account, including closed and disabled ones: status, admin flag, permission profile, last login, groups, and whether they can send envelopes, manage the account or call the API.