Organizational Roles and Functional Authority

This guide provides a comprehensive mapping of the functional roles and permission sets available within the IUSign Enterprise platform.

Prerequisites

• Assigned Admin or Owner role (to modify user assignments).
• Successful authentication into the IUSign portal.

Strategic Overview

Effective organizational governance is predicated on the granular delegation of authority based on the "Principle of Least Privilege." In IUSign, Roles define the operational capabilities and data visibility for every member of a tenant. By correctly mapping team members to their functional roles, administrators can ensure that sensitive document assets and administrative settings are protected from unauthorized access while enabling employees to execute their required workflows efficiently.

Role Hierarchy and Permission Manifest

The platform provides several predefined role categories designed to align with standard corporate hierarchies:

Role Definitions and Use Cases

1. The "Owner" Role (Primary Stakeholder)

The Owner is the ultimate administrative authority for the tenant.

• Authority: Full governance over all users, documents, and billing.
• Unique Capability: Only the Owner can delete the organization or modify the primary financial relationship with IUSign.
• Use Case: Typically assigned to the individual who initialized the IUSign account or a high-level executive lead.

2. The "Admin" Role (IT and Operations)

Administrators manage the day-to-day governance of the organization.

• Authority: Global visibility into all team documents, user provisioning, and organizational settings.
• Unique Capability: Can modify White-Labeling, configure API Keys, and manage roles for other users.
• Use Case: Ideal for IT managers, departmental leads, and operations personnel.

3. The "User" Role (Standard Employee)

The most common role for individuals who send and sign documents.

• Authority: Can create, send, and manage their own envelopes and templates.
• Visibility: Restricted to their own documents unless a transaction is specifically shared.
• Use Case: Sales representatives, HR coordinators, and procurement specialists.

4. The "Viewer" Role (Audit and Legal)

A specialized, non-participatory role for oversight.

• Authority: Read-only access to organizational document lists and Audit Logs.
• Constraint: Cannot initiate transactions, sign documents, or modify any settings.
• Use Case: Internal auditors, legal counsel, and compliance officers.

Strategic Considerations for Administrators

• Minimizing Risk: Most team members should be assigned the User role. Limit the Admin role to a small subset of trusted personnel who require operational governance.
• Lifecycle Management: Regularly review the user list in the Admin Dashboard to ensure that roles still align with actual job requirements.
• Group Sharing: If standard Users need to collaborate on documents, utilize Signing Groups instead of granting global Admin access.

Diagnostic and Resolution Protocols

Related Documentation

• Identity Governance and Team Scaling
• Functional Role Governance and Permission Mapping
• Admin Dashboard: Strategic Command Center
• Global Forensic Auditing and Reporting