39. Metadata and permissions
Module 8 · 20 minutes · Lesson 38; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use metadata and permissions without changing the wrong data?
- Explain metadata and permissions in your own words
- Trace the actual files state change from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
Sharing is a security decision, not a cosmetic property. Private resources should stay private unless a specific reviewed requirement justifies sharing. Inspect metadata and access before publishing or sending links. The local adapter records a coarse access level and does not emulate domain policies, ACL inheritance or shared-drive roles.
Example 1: Working automation
The normal result remains private. A link-sharing mutation is visible in the audit state.
function main() {
const file = DriveApp.getFileById("brief");
file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
console.log(file.getSharingAccess());
}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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: console.log(file.getSharingAccess());
- 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": [
"PRIVATE"
],
"error": null,
"resource": "files",
"value": {
"brief": {
"name": "Brief.txt",
"folder": "root",
"content": "Sample project brief",
"sharing": "PRIVATE"
},
"template": {
"name": "Letter template",
"folder": "root",
"content": "",
"sharing": "PRIVATE"
}
}
}Example 2: Investigate a reproducible failure
Predict the effect of DriveApp.Access.ANYONE_WITH_LINK and identify the first mismatch. This example is intentionally faulty.
function main() {
const file = DriveApp.getFileById("brief");
file.setSharing(DriveApp.Access.ANYONE_WITH_LINK, DriveApp.Permission.VIEW);
console.log(file.getSharingAccess());
}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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: file.setSharing(DriveApp.Access.ANYONE_WITH_LINK, DriveApp.Permission.VIEW);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: console.log(file.getSharingAccess());
- 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": [
"ANYONE_WITH_LINK"
],
"error": null,
"resource": "files",
"value": {
"brief": {
"name": "Brief.txt",
"folder": "root",
"content": "Sample project brief",
"sharing": "ANYONE_WITH_LINK"
},
"template": {
"name": "Letter template",
"folder": "root",
"content": "",
"sharing": "PRIVATE"
}
}
}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 file = DriveApp.getFileById("brief");
file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
console.log(file.getSharingAccess());
}
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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: console.log(file.getSharingAccess());
- 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": [
"PRIVATE",
"PRIVATE"
],
"error": null,
"resource": "files",
"value": {
"brief": {
"name": "Brief.txt",
"folder": "root",
"content": "Sample project brief",
"sharing": "PRIVATE"
},
"template": {
"name": "Letter template",
"folder": "root",
"content": "",
"sharing": "PRIVATE"
}
}
}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 file = DriveApp.getFileById("brief");
file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
console.log(file.getSharingAccess());
}
function main() {
console.log("Start: Metadata and permissions");
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 file = DriveApp.getFileById("brief");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: console.log(file.getSharingAccess());
- 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: Metadata and permissions");
- 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: Metadata and permissions",
"PRIVATE",
"Completed operation"
],
"error": null,
"resource": "files",
"value": {
"brief": {
"name": "Brief.txt",
"folder": "root",
"content": "Sample project brief",
"sharing": "PRIVATE"
},
"template": {
"name": "Letter template",
"folder": "root",
"content": "",
"sharing": "PRIVATE"
}
}
}Build and test
Repair the supplied script so that: The normal result remains private. A link-sharing mutation is visible in the audit state. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const file = DriveApp.getFileById("brief");
file.setSharing(DriveApp.Access.ANYONE_WITH_LINK, DriveApp.Permission.VIEW);
console.log(file.getSharingAccess());
}Graduated hints
Hint 1
Inspect the operation containing DriveApp.Access.ANYONE_WITH_LINK. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns DriveApp.Access.PRIVATE. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses DriveApp.Access.PRIVATE where the broken source uses DriveApp.Access.ANYONE_WITH_LINK. Explain why before applying it.
Reference solution
function main() {
const file = DriveApp.getFileById("brief");
file.setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW);
console.log(file.getSharingAccess());
}Explain and reflect
Which operation proves the intended result in metadata and permissions? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and files output 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 files 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.