Card issuance and activity reports

Understand the issuance register

The register records the issuer, recipient, issuance date, card type, branch and department alongside current active, suspended or revoked status. Card updates and lifecycle changes have an access-controlled activity history.

An organization can enable a one-active-card-per-staff-member policy. This prevents duplicate active staff cards; it does not erase earlier issuance records.

Issue and change status in bulk

1. Confirm your card management permission and the organization scope.
2. Choose Issue staff business cards and select up to 50 staff recipients. Review the shared title before issuing.
3. Open the created cards to add approved contact fields and review public visibility. Bulk issuance starts with company name, title and logo visibility.
4. Use the permitted bulk status action to suspend or revoke selected cards. Check the register and open a revoked public URL to confirm it is unavailable.

Read activity without overstating it

Reports distinguish total cards ever issued from currently active, suspended and revoked cards. Date-filtered engagement includes recorded QR requests, profile views, shares, vCard downloads, contact-action clicks and contact exchanges.

Inspect employee, branch and department breakdowns and the most-engaged cards. QR requests are observable requests, not verified physical camera scans. Shares and clicks do not prove delivery, a completed call or a message sent. Downloads do not prove contact imports. Unique visitors are not estimated.

Recognized bots and duplicate event keys are filtered where supported, but unrecognized automation can still affect counts. Cardholders see only their own permitted statistics; organization reports and CSV exports require the corresponding access.

Retention and exports

Authorized administrators can set event and activity-history retention in the card policy. The configured retention job must run; setting a number alone does not delete data. Expired events, scans and contact exchanges follow event retention; activity history follows its own period.

Issuance snapshots and reserved QR identifiers remain. Aggregate reports based on retained events can change after pruning. Exported CSV files are outside application access controls and need secure storage and disposal.