DiscoveryVIP / Apps Script AcademyHelp

75. Deploying and configuring access

Module 15 · 20 minutes · Lesson 74; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use deploying and configuring access without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

Deployment settings determine who may open a web app and whose authority it uses. A working local preview does not validate real Google identity rules. Start with a restricted test deployment and a sample workbook. Review scopes, server validation, ownership and data exposure before expanding access. The exercise produces a concrete deployment checklist as data.

Example 1: Working automation

The checklist fails closed when identity review is missing; it is not a real deployment API.

function main() {
  const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
  if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
  console.log(JSON.stringify(policy));
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 4: console.log(JSON.stringify(policy));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "{\"audience\":\"testers\",\"identityReviewed\":true,\"inputValidation\":true,\"sampleDataOnly\":true}"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of identityReviewed: false and identify the first mismatch. This example is intentionally faulty.

function main() {
  const policy = {audience: "testers", identityReviewed: false, inputValidation: true, sampleDataOnly: true};
  if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
  console.log(JSON.stringify(policy));
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const policy = {audience: "testers", identityReviewed: false, inputValidation: true, sampleDataOnly: true};
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 4: console.log(JSON.stringify(policy));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": "Deployment review incomplete",
  "resource": "logs",
  "value": null
}

Example 3: Separate setup from execution and inspect repeat behavior

Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.

function lessonAction() {
  const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
  if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
  console.log(JSON.stringify(policy));
}
function main() {
  lessonAction();
  lessonAction();
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 4: console.log(JSON.stringify(policy));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 8: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 9: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "{\"audience\":\"testers\",\"identityReviewed\":true,\"inputValidation\":true,\"sampleDataOnly\":true}",
    "{\"audience\":\"testers\",\"identityReviewed\":true,\"inputValidation\":true,\"sampleDataOnly\":true}"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 4: Add a diagnostic boundary around the operation

Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.

function lessonAction() {
  const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
  if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
  console.log(JSON.stringify(policy));
}
function main() {
  console.log("Start: Deploying and configuring access");
  try { lessonAction(); console.log("Completed operation"); }
  catch(error) { console.error("Failed operation: " + error.message); throw error; }
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 4: console.log(JSON.stringify(policy));
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: console.log("Start: Deploying and configuring access");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: catch(error) { console.error("Failed operation: " + error.message); throw error; }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 10: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Deploying and configuring access",
    "{\"audience\":\"testers\",\"identityReviewed\":true,\"inputValidation\":true,\"sampleDataOnly\":true}",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: The checklist fails closed when identity review is missing; it is not a real deployment API. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const policy = {audience: "testers", identityReviewed: false, inputValidation: true, sampleDataOnly: true};
  if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
  console.log(JSON.stringify(policy));
}

Graduated hints

Hint 1

Inspect the operation containing identityReviewed: false. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns identityReviewed: true. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses identityReviewed: true where the broken source uses identityReviewed: false. Explain why before applying it.

Reference solution

function main() {
  const policy = {audience: "testers", identityReviewed: true, inputValidation: true, sampleDataOnly: true};
  if (!policy.identityReviewed || !policy.inputValidation) throw new Error("Deployment review incomplete");
  console.log(JSON.stringify(policy));
}

Explain and reflect

Which operation proves the intended result in deploying and configuring access? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.

Troubleshooting

If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.

Knowledge check

Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.

Optional AI practice

Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.

Transfer to Google and authorization guide

Next lesson: APIs and HTTP requests