We lack a clear policy and different people use different encryption and retention practices, causing compliance gaps.…
Obtain OAuth2 credentials (Client ID, Client Secret) for your Adobe organization from the Adobe Developer Console.
Best practiceEnsure your credentials are up to date, as Adobe periodically updates API authentication requirements.
Request an access token by making a POST request to the Adobe Identity Platform token endpoint using your credentials.
NoteYou must use the appropriate scopes for Admin or Storage Management APIs to manage retention policies.
Identify the correct API endpoint for retention policy management—typically the Storage Management API or Catalog Service API for TTL (Time To Live) configuration.
NoteRefer to Adobe's Storage Management API or Catalog Service API documentation for the latest endpoint URLs and request formats.
Construct a JSON payload specifying the retention rule parameters, such as the number of days to retain documents, and the event that triggers retention (e.g., agreement completion).
CautionRetention policies only apply after an agreement reaches a terminal state (completed, canceled, or expired).
Send a POST or PATCH request to the retention policy endpoint with your access token and JSON payload to create or update the retention policy.
NoteUse POST to create a new policy and PATCH to update an existing one, as per API documentation.
To verify, send a GET request to the same endpoint to query and confirm the current retention policy settings.
Best practiceAlways validate the policy state after changes to ensure compliance and prevent accidental data loss.
Retention policies are not managed in the Acrobat desktop app; use the Admin Console or API for enterprise retention configuration.
Use the Adobe Storage Management API or Catalog Service API endpoints to programmatically set, update, or query retention (TTL) policies for enterprise content.
A document's 'terminal state' means it is finished and will not be changed anymore. Retention policies are applied at this point. This ensures the final version is kept for the correct amount of time, starting from when it is complete.
Acrobat's Enterprise Policy Retention helps your company follow HIPAA rules by letting you set specific times for how long patient documents are kept. You can define policies for 1 to 5475 days. These policies use password or certificate protection. This ensures sensitive health information is managed according to legal requirements and is secure. It helps you meet compliance standards like HIPAA, PCI DSS 3.0, SOC 2 Type II, and ISO 27001.
Acrobat's retention policies, known as Enterprise Policy Retention, focus on how long documents are kept within Acrobat itself, often applied to files after they are finalized. These are set by an admin and use password or certificate protection. Acrobat Sign, on the other hand, has its own data governance and retention configuration specifically for electronic signatures and related documents. While both deal with retention, Acrobat policies are for general document management, and Acrobat Sign policies are for signed agreements.