Every entry on DA Form 7789 exists because a record system needs it in writing. The form's official title is PRIVILEGED ACCESS AGREEMENT (PAA) AND ACKNOWLEDGMENT OF RESPONSIBILITIES, and it is raised whenever an office must privileged access agreement (paa) and acknowledgment of responsibilities in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 02/01/2023, status ACTIVE, is what stands here, spread across 1 page(s) and about 67 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give. A later edition has since been published, which is why this one remains: records executed against it must still be readable in the terms they were written.
The form has an author and an occasion, held by different authorities. CIO owns the content and reshapes it when what is being recorded changes. AR 25-2 governs the event that calls for the form and the route the finished document takes afterwards. Keeping those two apart is what allows a procedure to be amended without the page being rebuilt each time.
Identification precedes substance for a structural reason. Name, identification number, organisation and date of preparation are how the finished document is located in a file or a database; the body of the form is what someone reads after the search has succeeded. Spell the name as official records spell it, since the search runs against those records and not against habit.
Much of the form's behaviour follows from its being a fixed page. Tab order was set at build time along the reading sequence, which is why tabbing catches boxes a pointer passes over. Exclusive groups release one choice when another is made because a record cannot carry two answers to a single question. Single-line fields refuse to wrap because every entry must print where the layout expects it — text beyond the width is lost at the margin, visible on screen to the end. That is what remarks areas and continuation sheets are for. Marking a field that does not apply matters for a related reason: emptiness is ambiguous, and a reviewer reading the file later cannot distinguish an omission from a decision.
A signature is what converts entries into a record, which is why it comes last and why an unsigned form remains a draft however complete it looks. Where a reviewing official, an approving authority or a witness also signs, each adds a distinct attestation, and each dates the day of signing rather than the day of preparation — the dates trace the sequence of responsibility. The recurring defects are worth knowing precisely because they defeat that purpose: an empty mandatory field leaves an obligation unmet, transposed identification digits attach the record to nobody, a date with day and month reversed puts events in the wrong order, and entries left in a reused working copy assert facts nobody intended.
Personal information may not be gathered silently, and the Privacy Act statement is how that obligation is met on paper: it names the collection authority, the purpose, the routine uses and whether disclosure is mandatory. Because it exists to inform a decision, it belongs before the fields it covers rather than after them. A filled copy then holds personal data and is stored and transmitted under the corresponding safeguards.
Download the form
The published formats — PDF — reflect the range of places a form gets filled in. Where there is a computer, the fillable pdf supplies live fields that keep entries positioned and readable. Where there is not, the printable pdf gives the identical page as flat artwork for pen entry. The distinction is one of setting rather than of authority; the page is the same document in both.
The choice of application decides whether your work survives. Browsers render pdfs as documents to be read; where a viewer shows fields without a mechanism to store them, typed text disappears when the tab closes, and nothing announces the loss. A full reader treats the file as a form and preserves entries on save.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- APPROVED
- ATCTSReg
- CSAUP
- CyberAware
- DENIED
- Form_Rectangle
- ISName
- ISName2
- ISSMName
- ISSM_Date
- ISSM_sign
- JWICS
- MPG1
- MPG2
- NIPR
- NSA
- Organization
- Page1
- Page2
- R13
- R23
- R33
- R43
- R53
Disposition is prescribed, not chosen. AR 25-2 names the destination, whether that is a specific office, the unit administrative channel or the personal record, and the applicable records schedule governs how long it survives there. Both rules exist to keep the file consistent across offices with different habits. Take your copy before the document leaves, since it will not come back.
Related documents are located by series and number, and the relation is rarely accidental — forms under one proponent or one directive tend to serve steps of a single procedure. Anything the DA series form names on its face normally travels with it, as do the continuations, covers and transmittals the process generates. Assembling them together is what makes the submission a complete account.
Editions change because the process changes, and the printed edition date is the only marker of which version a page belongs to. A copy saved locally cannot know it has been superseded, so the date on it is compared against the edition in force before reuse. Records already executed under an earlier edition are left alone — a document is read under the terms it was made, and reopening completed files to match a later form would falsify the account.
One boundary should be stated clearly. What is distributed here are copies of published Department of the Army forms; the site is independent, issues nothing of its own, and holds no position in the system it describes. Proponency, prescribing directives and retention schedules operate without reference to it. Consequently nothing here is legal advice and no assurance about acceptance is possible. Questions about a particular entry, a requirement or eligibility belong with CIO or your servicing administrative office.
Questions and answers
- What is DA Form 7789?
- PRIVILEGED ACCESS AGREEMENT (PAA) AND ACKNOWLEDGMENT OF RESPONSIBILITIES
- Which edition is current?
- 02/01/2023
- Who is responsible for this form?
- CIO
- In which formats can it be downloaded?
- PDF, PDF
Publisher notes
- , PREVIOUS EDITION DATED MAR 2019 MAY BE USED.