How to Send Password Protected Power BI PDF Reports

The accounts team has approved the figures. Each customer should receive a statement containing only their transactions, with a password required to open it. Customers may need to print a copy for their records, but the team does not want the statement casually edited before it is passed around.

Doing that once is manageable. Repeating it for every customer means moving between the report, a PDF utility and an email message, checking the same details again and again. A late correction can send the whole process back to the beginning.

PBRS brings report selection, PDF preparation and delivery into one recurring job. Its standard PDF output settings include separate user and owner passwords, 128-bit encryption and controls for permitted document actions. The accounts team can maintain those choices in PBRS rather than maintain a separate protection script or bolt-on PDF service.

Protect the right statement for the right person

Start with the customer’s report filter or parameter, then match the output to the intended recipient. PBRS can use data-driven values to personalize passwords and security settings alongside the content and delivery details. This is useful when each customer needs their own document rather than everyone receiving the same attachment.

Protection and personalization work together. A password controls access to the file; the customer selection determines whose transactions are inside it. Keep both tied to the same customer record.

PBRS works with published reports in Power BI Service, Power BI Report Server and SSRS. It does not export directly from Power BI Desktop. Publishing the report gives the recurring job a shared source to use without depending on someone opening a local PBIX file.

For the monthly statement, there are two different questions: who may open the file, and what may they do once it is open? PBRS gives you separate settings for each.

Two passwords, with different jobs

The user password, also called the document-open password, is the password the customer enters to read the PDF. Use it when the contents should not be visible merely because someone has a copy of the attachment.

The owner password protects the document’s permissions. Keep it with the person responsible for administering the PDF, rather than sharing it as the customer’s opening password. Set the two passwords separately; an owner password by itself is not a substitute for requiring a password to open the document.

PBRS documents 128-bit PDF encryption for its File Permissions options. These controls are built into PBRS’s PDF output configuration, so the standard protection step does not require you to purchase a PDF add-in or write a post-export encryption script.

Choose the actions the reader needs

Perhaps the customer should be able to print the statement and add a note while reconciling an invoice, but should not edit the figures. PBRS exposes individual permissions so you can make that choice deliberately.

Choose the settings around the customer’s task, including accessibility needs. These are PDF permissions, whose enforcement depends on the reader software; they are not a guarantee that an authorized reader cannot capture or share information they can see.

For a one-off file, an approved PDF tool may be enough. For recurring statements, PBRS saves the team from repeating the same export, protection and sending steps. The protection becomes part of the maintained reporting job.

Passwords are only part of a finished statement. The reader also needs to recognize the document, understand how it should be handled and find the right version later. PBRS can prepare those details in the same workflow.

Add a watermark people can understand

Use a text watermark or stamp for a notice such as “Confidential,” or use a graphic such as your company logo. Recipient information can make a personalized document easier to identify. Position the watermark so it communicates the message without obscuring balances or transaction details.

A watermark provides a visible handling cue. It complements encryption and permissions; it does not replace them.

Give the file useful metadata

PBRS’s File Summary settings let you set document properties, such as the author and summary information, as part of producing the PDF. This helps the saved file carry useful context instead of unexplained properties inherited from the original report.

Give the output a recognizable filename too—for example, a statement identifier and reporting month. File properties and filenames serve different purposes: one describes the document, while the other helps the customer find it in a folder.

The PDF settings guide explains that leaving a File Summary property empty preserves the original value. To overwrite a property with a blank, enter a space. Review the finished file’s properties rather than assuming an empty setting removed inherited information.

Configure the recurring statement

1. Select the report and customer. Set the correct filter or parameter, and schedule the job after the reporting data is ready.
2. Choose the PDF destination. Select Acrobat Format (*.pdf), open Format Options and enable PDF options.
3. Apply protection. Set distinct user and owner passwords, select the required document permissions, and add the watermark.
4. Finish the presentation. Set File Summary properties and the output filename, then configure the recipient and message.
5. Check the delivered statement. Test opening it with no password, an incorrect password and the intended user password. Check printing, other chosen permissions, the watermark and file properties.

These are built-in PBRS settings. Once configured, PBRS can apply them each time the job runs; your team does not need an additional script to protect or stamp every exported PDF. The PBRS PDF settings guide shows the controls.

Carry the same care into larger deliveries

If a customer needs a statement and supporting reports, PBRS can combine supported outputs into one ordered PDF. Check the protection on that final merged document. You can also use encrypted, password-protected ZIP output when an archive suits the receiving process; protecting an archive is separate from protecting each PDF inside it.

For data-driven delivery, test at least two customers and decide how a missing password should be handled. Keep each customer’s content, recipient and protection values together, and verify that the workflow follows your policy rather than assuming an empty password automatically stops the job.

PBRS also offers standard PDF expiry settings with a custom expiry message. Optional DRM adds controls such as approved email addresses, device limits and permitted print attempts; that optional feature requires a separate All-About-PDF Developer License. The built-in passwords, encryption, permissions, watermarks and metadata discussed above do not require that add-on.

You do not need the API to use PBRS’s PDF protection. The accounts team can configure and schedule the complete process in PBRS. An API becomes useful when a billing application knows exactly when the month has closed and should start the already configured job.

Keep the passwords, permissions and watermark settings in the tested PBRS schedule. The application requests execution; it does not need to implement its own PDF encryption or stamping routine.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: bearer <access-token>
Content-Type: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Monthly statement ready"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-execution-id>
Authorization: bearer <access-token>

Keep the execution identifier with the statement month and customer reference, while keeping passwords out of ordinary logs and request URLs. After a configuration change, inspect a delivered test file before returning the job to its regular audience.

Next month, the accounts team should be reviewing the figures and answering customer questions—not opening a PDF utility for every statement. The customer receives a recognizable file, uses the agreed password and can perform the actions needed to reconcile the account.

PBRS makes that preparation repeatable. Export, encryption, passwords, permissions, watermarks, metadata and delivery can be maintained together, without adding a separate PDF protection script to the team’s workload.

Explore PBRS PDF automation and the wider Power BI Report Automation workflow. Use the evaluation guide below to try a representative customer statement and its complete delivery process.

Download the PBRS Internal Evaluation Guide