Wedding Guest Spreadsheet Permissions: Avoiding Accidental Exposure

Who can open, copy, and change your guest list: link settings, a column matrix, and a clean close-out

47 minutes read
Wedding Guest Spreadsheet Permissions: Avoiding Accidental Exposure guide cover graphic

Wedding guest spreadsheet permissions decide who can see, copy, and change the one file that holds your guests’ names, addresses, phone numbers, and meal needs, so setting them on purpose, before the first helper gets a link, prevents most accidental exposure.

Quick answer

Start with the sharing setting, not the password. Set general access to Restricted, invite named people by email, and give each one the lowest role that covers their task: viewer for reading, editor only for the one or two people who maintain the list. Split sensitive columns, such as home addresses and allergy notes, into a couple-only tab or file. Turn on two-step verification for the account that owns the sheet, and remember that view-only people can often still make copies, so share only what each person truly needs. Review who has access on a set date, and close the sheet after the wedding.

A guest spreadsheet starts as a harmless list. Within a few weeks it has a column for addresses, another for dietary needs, one for which cousin is bringing whom, and a link that three relatives have forwarded to other relatives. Nobody was careless on purpose. The file simply grew faster than the habits around it. This guide walks through wedding guest spreadsheet permissions in the order you will meet them: what is actually in the file, what each sharing setting really does, how to match access to roles, how to protect the sign-in behind the file, where copies escape, and how to close the whole thing down when the wedding is over.

It is general consumer education, not legal, security-compliance, or privacy advice. Rules about personal data differ by state and country, and a spreadsheet that serves a business, such as a planner’s client list, may carry obligations a couple’s file does not. When in doubt about a specific legal duty, ask a qualified professional.

Why wedding guest spreadsheet permissions get overlooked

Most people think about security when they are handling money or a password. A guest list feels social, not sensitive, so it rarely gets the same attention. That gap is where accidental exposure lives, and understanding it makes the fixes feel proportionate instead of paranoid.

What a guest spreadsheet really contains

Look at your sheet as a stranger would. The first impression is a list of names, but the details underneath are what make wedding guest spreadsheet permissions worth a few minutes of care.

More than names

A typical guest file collects full names, mailing addresses, phone numbers, email addresses, relationships, plus-one details, children’s names and ages, meal choices, and notes that guests shared in confidence. Taken together, that is a ready-made directory of households, many of them with older relatives and young children. Guests gave you those details so you could invite and feed them, not so a stranger, a vendor’s intern, or a friend of a friend could use them. Our guide to the wedding RSVP data export looks at the same information from the website side.

Notes that reveal health or family situations

The columns that deserve the most care are often the least obvious. A dietary note such as “celiac” or “severe nut allergy” can hint at a health condition. An access note about a wheelchair or hearing support is personal. A comment such as “do not seat near the ex” or “estranged, only invited out of obligation” is the kind of sentence that causes real hurt if it travels. When you review your wedding guest spreadsheet permissions, treat these columns as the most sensitive part of the file, because the harm from showing them is social and emotional, not only technical.

How accidental exposure usually happens

Few exposures involve a break-in. They tend to come from ordinary generosity and convenience, and naming the common routes helps you close them calmly.

Link sharing is the single biggest source of surprise. Google’s help page explains that when general access is set to Anyone with the link, anyone who has the link can open the file without signing in. A link that was meant for your sister can be pasted into a family group chat, forwarded to an aunt, and screenshotted into a message thread. The more people who hold the link, the less you know about who has it. Microsoft describes the same behavior for OneDrive: an Anyone link works even if it is forwarded beyond the original recipient.

The helpful editor

The second route is a well-meaning editor. By default on Google files, editors can share the file and change permissions, though the owner can turn that off. A bridesmaid who is asked to fix a typo can, in the same session, add her partner to the file so he can “help with the seating.” There is no malice in it. There is also no record in your head that it happened. Learning what each role can do is the heart of good wedding guest spreadsheet permissions. Editors are the part of wedding guest spreadsheet permissions that surprises people most.

The attachment and the copy

The third route is the copy. Someone downloads the sheet to open it offline, emails it to a vendor, or saves it to a shared computer. The original may be locked down perfectly while a dozen copies live in inboxes and download folders. We return to this later, because copies are the part of wedding guest spreadsheet permissions that settings alone cannot fix.

Who is actually at risk

It helps to name the real downside, not to alarm yourself but to decide how much effort each part of the file deserves.

Your guests

The people most affected are your guests. An address that reaches a marketer produces junk mail. An address and a date that reach someone malicious can reveal when a household will be away for the weekend. A guest whose health note becomes public did nothing to deserve it. Because the information is theirs, treating it carefully is part of hosting.

You and your helpers

You are affected too. A leaked list is embarrassing, it creates awkward conversations with relatives, and in the worst case it hands a scammer a list of real names and relationships to build convincing messages from. The Federal Trade Commission’s scams hub lists phishing and impersonation among the scam types consumers face, and a wedding guest list gives an impersonator a lot to work with. We cover those messages in our guide to wedding website scam messages.

Take stock before you change any setting

The most useful thing you can do for wedding guest spreadsheet permissions happens before you touch a sharing dialog: find out what you have, where it lives, and who already holds it. The Federal Trade Commission’s guide for businesses on protecting personal information begins the same way, with the instruction to map where sensitive data sits and how it moves. It is written for companies, but the first step translates cleanly to a couple with a spreadsheet.

Find every copy of the list

You probably have more versions than you think, and each one has its own sharing setting.

Search your own accounts

Search your email for attachments with words like “guest list,” “RSVP,” and “seating,” and check the downloads folder on every laptop you use. Search your cloud storage by file name. Look at your phone’s files app. Note each copy, who has it, and whether it is a working file or an old draft. Old drafts are the ones most likely to be forgotten while still shared. Good wedding guest spreadsheet permissions start with knowing what exists.

Ask the helpers what they hold

Send a short, friendly message to each person who has ever had the file: “I am tidying up our guest list access. Do you still have a copy, and where is it?” Most people answer honestly and without fuss, and a few discover a download they forgot. Frame it as housekeeping, not suspicion, and treat the answers as your starting inventory for wedding guest spreadsheet permissions.

Triage the columns by sensitivity

Not every column carries the same risk. A three-level triage keeps the rules simple enough to follow while you are busy.

Level one: columns almost anyone helping can see

Names as guests will see them printed, party size, table number once seating is final, and RSVP status are usually fine for a helper who is working on seating or place cards. Our wedding seating chart guide explains why a seating helper does not need contact details to do the job. At this level, wedding guest spreadsheet permissions can be generous.

Level two: need-to-know columns

Meal choice, shuttle pickup point, hotel block, and the phone number of a guest who needs transportation belong in the file only for the person who needs them. A caterer needs meal counts. A transport lead needs pickup points. Neither needs the other’s columns. This is where wedding guest spreadsheet permissions turn from a settings question into a design question: who gets which columns.

Level three: couple-only columns

Home addresses, personal phone numbers and email addresses, health-related dietary notes, access needs, and private comments belong to the couple and to no one else unless a specific, narrow task requires them. Even then, share a trimmed export, not the master file. Our guide to wedding dietary restrictions explains what a caterer actually needs and why a single flag often beats a long note.

Wedding guest spreadsheet permissions: guest sheet columns sorted into three sensitivity levels, from names and table numbers to addresses and private notes
Which columns does each job need? Eight example columns sorted into three levels of sensitivity.Source: MyWeddingSource editorial framework; adjust to your own list.

The picture above shows one way to draw the three levels on a sheet. The labels are our own editorial framework, not a standard, so adjust them to your guest list.

How sharing settings actually work

Most mistakes in wedding guest spreadsheet permissions come from misreading one dialog. The words are short and the consequences are large, so it is worth reading them slowly once. The details below come from Google’s and Microsoft’s own help pages. Menus change, so confirm what you see in your own account.

Whether you use Google Sheets or an Excel file stored in OneDrive, the first question the dialog asks is who can open the file at all.

Restricted: only the people you named

Google describes Restricted as the setting in which only people who have been given access can open the file. This is the setting to choose for your guest list. It means a forwarded link is useless to anyone you did not invite, because they will hit a request-access screen, not your data. Microsoft’s equivalent is a link for specific people, which works only for the people you name, even if the invitation is forwarded. For wedding guest spreadsheet permissions, this is the baseline.

Google describes this setting as letting anyone with the link open the file without signing in, at whichever role you choose. Convenience is the appeal, because nobody has to log in. That is also the problem. You have no list of who opened it, and the people who did are shown as anonymous visitors. For a file full of guest details, this is rarely the right choice, and you can usually get the same convenience by inviting specific email addresses.

Public on the web: almost never appropriate

Google also describes a public option in which anyone can find the file through search. There is no scenario in which a guest list should be set that way. If you are ever unsure what a file is set to, open the sharing dialog and look at the general access line first.

Three link-access settings for a guest spreadsheet drawn as doors: restricted, anyone with the link, and public on the web
Three doors into one guest sheet. How far each general-access setting opens the file.Source: MyWeddingSource illustration of settings described in Google and Microsoft help pages.

The drawing shows the three doors in order of how much you give up at each one. It is our own illustration of the settings the two providers describe.

What each role can really do

The second question is what each person may do. Google describes four roles, and the differences are what make wedding guest spreadsheet permissions work.

Viewer and commenter

A viewer can open the file but cannot edit it, comment on it, or share it. A commenter can view and comment but not edit or share. Google notes that downloading is allowed by default for both, though the owner can turn that off. This is the important caveat: view-only does not mean copy-proof, and the same help page for protected ranges notes that view-only users can make a copy of the spreadsheet. Treat viewer access as “can read,” not “cannot take.”

Editor and owner

Editors can view, comment, edit, download, and share, and by default can also change permissions, which the owner can turn off. The owner keeps full control. If you have two partners planning the wedding, decide now which of you is the owner of the master file and which is an editor, and write it down, because transferring ownership later is a separate procedure that Google’s sharing page links to separately. We did not verify those steps, so check Google’s own article if you need them.

Turn off the extras that you do not need

Google’s help page describes settings that stop editors from changing permissions and sharing, and lets you choose which roles can download, copy, and print. The same page notes an important limit: turning off editor resharing on one file does not cover the parent folder, and an editor of the folder can still give someone access to the file. Check the folder, not only the file. These switches are the quiet workhorses of wedding guest spreadsheet permissions.

A decoder for the dialog

Because the dialog is short, people guess. The table below translates the options into plain consequences for a guest list.

Read the table row by row

The table is our own summary of what Google and Microsoft describe, not a substitute for their help pages. Read it from the top, because the first three rows answer who can open the file and the rest answer what they can do once inside. Most couples find that two or three changes cover everything.

Sharing settings decoded for a guest list
SettingWhat the provider describesWhat it means for your guest listOur suggestion
Restricted (Google) or specific people (Microsoft)Only named people can open itA forwarded link does not work for strangersDefault for the master file
Anyone with the linkAnyone holding the link can open it, no sign-in neededYou lose track of who has seen itAvoid for guest details
Public on the webThe file can be found through searchEquivalent to publishing the listNever
Viewer or commenterCan read, and by default can downloadCan still keep a copyUse for helpers who only read
EditorCan edit, share, and by default change permissionsCan invite others without telling youLimit to one or two people
Editors may share: offThe owner keeps control of who is addedOnly the owner adds peopleTurn off
Download, print, copy: off for viewersBlocks those actions for that roleRaises friction, not a guaranteeTurn on for read-only helpers

Where the settings stop helping

The last two rows deserve a caution. Google’s page says that sharing content in other ways cannot be prevented, which means a determined person can still photograph a screen. These settings reduce casual spread. They do not make a file leak-proof, so the safest column is the one you never put in the shared file.

The permission matrix: who sees which columns

This is the working core of wedding guest spreadsheet permissions. A matrix answers a question that a sharing dialog cannot: not only who may open the file, but which parts of it each person should ever see. Think of it as a short written agreement with yourselves before anyone else is involved.

Build the matrix for your own team

Every wedding has a slightly different cast, so start by listing yours. The recipients below are common examples, not requirements.

List the people and their one job

For each person who touches the guest list, write a single sentence describing the job. “Maintains the master list” is one job. “Sets up the seating chart” is another. “Counts meals for the caterer” is a third. If you cannot describe a person’s job in one sentence, they probably do not need access to the file yet. A planner or coordinator may have a longer job description, and our guide to the difference between a wedding planner and a coordinator explains how those roles differ so you can decide how much of the file each one needs. Clear jobs make wedding guest spreadsheet permissions easy to defend.

Assign columns to jobs, not to people

Once the jobs are written, decide which columns each job needs. This is a subtle shift that makes wedding guest spreadsheet permissions much easier to explain. When your sister asks why she cannot see addresses, the honest answer is “the seating job does not need them,” which is about the task, not about trust. Nobody has to feel doubted.

The matrix itself

The table below is a worked template. The recipients and columns are examples, and the Yes, No, and Counts-only entries are our suggestions for a typical guest list, not rules from any standard.

A starting matrix to adapt

Guest column access by role. A template to adapt, not a standard
ColumnCouple (owners)Co-organizer (editor)Seating helperCatererTransport leadParent viewing totals
Guest nameYesYesYesYes, if needed for place cardsYes, for riders onlyNo, counts only
Home addressYesOnly for mailingNoNoNoNo
Email and phoneYesYesNoOnly if neededOnly for ridersNo
RSVP statusYesYesYesCounts onlyCounts onlyCounts only
Meal choiceYesYesNoYesNoCounts only
Allergy or health flagYesYesNoYes, as a flagNoNo
Access needsYesYesOnly seating needsOnly if relevantOnly if relevantNo
Plus-one and childrenYesYesYesCounts onlyCounts onlyCounts only
Table numberYesYesYesMaybeNoNo
Pickup pointYesYesNoNoYesNo
Private notesYesNoNoNoNoNo

What the matrix shows at a glance

Notice how short the Yes column gets once you read down it. Only the couple holds everything. The co-organizer holds nearly everything but not the private notes, and the others each see a narrow slice. A matrix also shows you which jobs to double-check. If the caterer’s column asks for a phone number, ask why. If a parent’s job is “knowing how many people are coming,” a single total cell serves the whole job. A good matrix makes wedding guest spreadsheet permissions visible to the whole team.

Turn the matrix into actual files

A matrix on paper does nothing until it becomes real access. There are three ways to do it, and they trade effort against safety.

Separate tabs inside one file

The simplest approach is one file with several tabs, such as a master tab, a seating tab, and a meal-counts tab. It is easy to maintain, but Google’s help page for protected ranges warns that protection is not a security measure and that anyone with access can print, copy, paste, or import and export copies. The same page says that hiding a sheet is not protection, because anyone with access can unhide it. So tabs inside one shared file organize the work. They do not keep a person away from data in the same file. Use them only for people who may see everything in the file anyway.

Separate files for separate jobs

The safer pattern is a master file that only the owners can open, with a trimmed export for each recipient. You maintain one source of truth and generate a small file per job: meals and dietary flags for the caterer, riders and pickup points for the transport lead, tables and names for the seating helper. It takes more effort, because you refresh the exports whenever the master changes, but it limits what any one leak can reveal. This is the single most effective habit in wedding guest spreadsheet permissions.

Counts instead of rows

For many recipients, rows are the wrong thing to share. A parent who asks “how many are coming?” needs one number. A venue that asks for a headcount needs one number. When the answer is a count, send the count, in a message, with no file at all. Our wedding venue capacity guide explains where counts matter for the venue, and a sentence in an email is a share that cannot be forwarded as a spreadsheet.

Keep a short access register for the sheet

The matrix says what should happen. A register records what did happen. It is a small table you keep in a file only the owners can open.

Fields worth recording

Sheet access register. One row per person or vendor, no passwords stored
FieldWhat to recordExample
Person or vendorName and roleSeating helper, a sibling
File or tabWhich file they can openSeating export, version two
Role givenViewer, commenter, or editorViewer
How access was givenNamed invitation, link, or emailed fileNamed invitation
Download allowed?Yes or noNo
ReasonThe one-sentence jobPlace cards and table plan
Access endsA date or an eventAfter final seating is printed
Date removedFilled in when you revokeFill in at the time

The example values are illustrations, not records. The point of the register is that on any given day you can answer “who can see what, and why?” in under a minute. Our guide to wedding planning password sharing describes a broader register for all accounts, and this one is its spreadsheet-specific cousin.

Review on a fixed date

Pick one date a month, for example the first Sunday, and open the register. Check the sharing dialog against it. Anyone in the dialog who is not in the register is a question to answer that day. Anyone in the register whose job has ended is a person to remove that day. Five minutes at a steady rhythm beats a frantic audit the week before the wedding. A monthly check keeps wedding guest spreadsheet permissions from drifting.

Protect the account behind the sheet

Excellent wedding guest spreadsheet permissions mean little if the account that owns the file can be taken over. Whoever signs in as the owner can change every setting you just chose. That is why the sign-in deserves as much attention as the sharing dialog.

Passwords that follow current guidance

Old rules about symbols and monthly changes have given way to simpler advice, and the simpler advice is easier to follow.

Length and uniqueness first

NIST’s current digital identity guideline, SP 800-63B, sets out requirements for the services that check passwords, not for you directly. Even so, its direction is clear and useful. It says a password used alone must be at least fifteen characters, while one used only as part of multi-factor sign-in may be shorter but at least eight. It tells services not to impose rules such as requiring particular mixes of character types, and to check chosen passwords against lists of commonly used or compromised values. For a couple, the practical reading is that a long, unique passphrase for your email and for the account that owns the sheet is better than a short one dressed up with symbols, and that reusing a password across sites defeats the point. Strong sign-in basics support every other part of wedding guest spreadsheet permissions.

No need to change on a schedule

The same guideline says services should not require people to change passwords periodically, while still requiring a change when there is evidence the password has been compromised. That is a relief for a busy planner. Instead of rotating on a calendar, change a password when something suggests a problem, such as an unfamiliar sign-in alert, or when someone who knew it should no longer have it.

Two-step verification, in plain terms

Two-step verification, also called multi-factor authentication, adds a second check after the password. It is the single most valuable setting on the account behind your guest list.

What the second step is and why it helps

The Cybersecurity and Infrastructure Security Agency, or CISA, explains that multifactor authentication asks you to confirm your identity with something besides your password, such as a code from an authenticator app, a code sent by text or email, or a fingerprint or face scan. If someone steals your password, they still cannot get in without the second step. CISA says to turn it on for every account that offers it, and singles out email as especially important, because attackers who take over an email account can often reset the passwords on other accounts. For a guest list, that means the email address attached to the account that owns your sheet matters as much as the sheet. Two-step verification is the lock on the door that wedding guest spreadsheet permissions open.

Choosing among the second steps

Google’s help page for 2-Step Verification describes several options. A passkey verifies you with a fingerprint, face, or device screen lock. A hardware security key is a small physical device that Google says offers strong protection against phishing. Google also describes prompts sent to a signed-in phone, authenticator apps that create codes without needing internet or mobile service, and text or voice codes, which the page describes as more vulnerable to phone-number-based attacks. CISA’s guidance likewise presents phishing-resistant options built on the FIDO standard as the strongest choice. A reasonable ladder for most couples is a passkey or authenticator app first, text codes only if nothing else is available, and printed backup codes stored somewhere safe, which Google also describes. We did not test these methods ourselves. Any of these upgrades the account behind your wedding guest spreadsheet permissions.

Sharing the file without sharing the account

The most common shortcut in wedding guest spreadsheet permissions is handing out the owner’s login. Avoid it.

Invite, do not hand over the login

A named invitation gives a helper their own sign-in and their own role, which you can remove without touching anyone else. A shared login does the opposite. It gives everyone the owner’s powers, leaves no record of who changed what, and cannot be revoked for one person alone. Our wedding planning password sharing guide covers this in more depth, including what to do when a vendor insists on a shared login. Named invitations are the cleanest form of wedding guest spreadsheet permissions.

Make the second step work for two partners

Couples sometimes lock themselves out by tying the second step to one phone. Add both partners’ phones or a second method to the account, and keep printed backup codes in a place you both know. Test the recovery path once while nothing is urgent. Accessibility matters here too. If a helper cannot easily use a text code or an authenticator app, a different method is better than none, and the Web Content Accessibility Guidelines, the technical standard the W3C publishes for web accessibility, exist to make web content usable by people with disabilities. Our wedding website accessibility audit goes deeper on that side of the planning.

What this actually costs

Nearly everything in this guide is free. Restricted sharing, role settings, version history, and two-step verification are built into the Google and Microsoft accounts most couples already have. The cost is time, and our own rough estimate is an evening to inventory and set up, and a few minutes a month to review. Some sharing controls, such as password-protected or expiring links in OneDrive, are described by Microsoft as needing a Microsoft 365 subscription, and Google describes some expiration options as limited to certain work or school accounts, so check what your plan includes before you count on them. We did not verify current prices. For the wider budget, see our wedding budget calculator.

Copies and exports: where the data escapes

Sharing settings control the original. They do not control what leaves it. A realistic approach to wedding guest spreadsheet permissions admits that copies will exist and plans which ones you can live with.

The copies you cannot recall

Once a file has been downloaded, emailed, or copied, no setting in the original can reach it. Knowing the routes helps you decide what to send and what to keep.

Download and make-a-copy

Google’s pages describe two things that matter here. Viewers and commenters can download by default unless the owner turns that off, and view-only users can make a copy of the spreadsheet. A copy made by someone else belongs to them, with its own owner and its own sharing. If you later remove that person from the original, their copy stays where it is. This is why the strongest form of wedding guest spreadsheet permissions is choosing what goes into a file before you share it, not relying on taking access back afterward.

Emailed attachments and vendor imports

An attachment is a copy that lives in at least two inboxes, plus every device that syncs them, and it can be forwarded further. Vendors often import the file into their own system, such as an order form, a rooming list, or a printing template. At that point the data sits under that vendor’s rules, not yours. Our guide to wedding vendor subcontractors explains why a vendor’s data may pass through hands you never met, which is another reason to send only the columns that vendor needs. Attachments fall outside wedding guest spreadsheet permissions entirely, so send fewer of them.

Routes by which copies of a guest spreadsheet escape the master file: download, copy, email attachment, vendor import, screenshot, and printout
Where copies of a guest sheet escape. Removing access does not recall what someone already saved or sent.Source: MyWeddingSource illustration; routes are not exhaustive.

The drawing above maps the routes from one master file to the places copies end up. It is our own illustration built from the behaviors the Google and Microsoft help pages describe.

Version history as a quiet safety net

Version history will not recall a copy, but it helps you understand what changed inside the original, which matters if an editor made a mistake.

What the history shows

Google explains that you open version history from the Last edit link at the top right, and that right-clicking a cell lets you see its edit history. It also lists limits: some changes, including added or deleted rows and columns, formatting changes, and changes made by formulas, do not appear in the cell history. You need edit permission to browse earlier versions, so a viewer cannot. That makes version history a tool for owners and editors, not a window onto who has looked at the file. We did not find a statement in the pages we read that describes a view log for personal files, so do not assume you can see who opened the sheet. Version history complements wedding guest spreadsheet permissions but does not replace them.

Restoring without losing the trail

To go back, you select an earlier version and restore it. Google notes that restoring clears the cell-by-cell edit history for changes made before the restore, and suggests making a copy of the spreadsheet first if you want to keep that history. A sensible habit before any big restore, or before handing the file to a new editor, is to make a dated copy that only the owners can open. Our wedding party group chat rules article explains how to keep a conversation about changes from turning into a pile of competing versions.

Build a trimmed export, not a forwarded master

For each outside recipient, the safest file is a small one created for them.

A short procedure

Make a fresh copy of the master, delete every column the recipient does not need, delete every row they do not need, and check the remaining sheets and hidden columns for leftovers. Google warns that hiding is not protection, so delete instead of hide. Share the trimmed file by invitation, set the role to viewer with download, print, and copy limited if your account allows it, and add an end date to the register. Then check the file once as the recipient would see it, using a private browser window or a second account. This procedure is the practical heart of wedding guest spreadsheet permissions for vendors.

Name, date, and retire every export

Give each export a name that says who it is for and when you made it, such as the vendor, the purpose, and the date. When a newer version goes out, remove access to the older one so that nobody works from stale numbers or keeps a file you thought was gone. Our wedding vendor timeline article shows when final counts are usually due, which tells you when to cut the last export for each vendor.

Vendor and source questions

Many of the people who ask for your guest list are professionals, and a good one will be glad you asked what they do with it. The questions below come from our own editorial judgment, not from any regulation, and they apply to venues, caterers, printers, calligraphers, transport companies, and planners alike.

Questions to ask anyone who wants your guest list

  • Which exact columns do you need to do this job, and which can we leave out?
  • Can we send it as a view-only file through a named invitation, instead of an email attachment?
  • Where will you store it, and who on your team will be able to open it?
  • Will you pass it to a subcontractor or another company, and if so, which one?
  • When will you delete it, and will you confirm the deletion in writing?
  • How should we reach you if we need to correct a name or take back access?
  • If you need a change, how will you contact us, so we can recognize a real message?

Before you send anything

A short pause before sending catches most problems.

Ask what they need and why

Start by asking the vendor to name the fields they need. Printers, for example, usually need a name and a mailing address, not a meal choice. Calligraphers need names and addresses, and rarely phone numbers. Our wedding calligraphy guide describes the usual hand-off, and if a vendor asks for the whole list, ask what the extra columns are for. A vendor with a reason will give it. A vendor without one may be collecting more than the job requires, which is exactly what the FTC’s guide for businesses tells companies not to do when it advises them to collect and keep only the sensitive data they really need. Vendors are the biggest outside audience for your wedding guest spreadsheet permissions.

Put the answers in writing

Record the vendor’s answers about storage, subcontractors, and deletion in an email or in the contract. Wording such as “we will delete the file within a set period after the event” is a reasonable request. A contract is where such promises belong, and our wedding vendor contract guide covers the clauses worth checking. Treat any claim a vendor makes about its own security as the vendor’s description, not as something you have verified.

Apps, add-ons, and AI tools

Spreadsheets rarely stay in one place. People connect add-ons, mail-merge tools, and assistants to them, and each connection is another party.

Third-party connections

Mail-merge and label-printing add-ons can be useful, and they can also ask for broad access to your files. The help pages we read do not list specific add-ons, so this is general advice from us: before you connect anything, ask what it can read and whether it keeps a copy, remove connections you no longer use, and prefer a trimmed export to granting a tool access to your master file. Disconnecting a tool does not necessarily delete what it already stored, so ask the provider about deletion too. Every connection widens your wedding guest spreadsheet permissions beyond the people you named.

Pasting the list into an AI assistant

It is tempting to paste a guest list into an AI assistant to sort it, draft messages, or build a seating plan. Treat that as sending the list to another outside party. Check the tool’s own data policy first, paste only the columns you would be comfortable sharing, and consider replacing names with codes. Our guide to using AI to summarize wedding proposals without sharing sensitive data covers the same habits for another kind of file, and our guide to AI wedding planning looks at the broader picture.

Checking who is really asking

Guest lists are attractive to scammers because they contain real names and relationships. A request that looks routine may not be.

The request that arrives out of nowhere

The FTC describes phishing as a message, often by email or text, that pretends to come from a business you may deal with and pushes you toward a link or attachment. A message that claims to be your venue and asks you to “confirm the guest list” by clicking a link fits that pattern. The FTC’s advice is to avoid clicking links or opening attachments in a message you did not expect, and if you do have an account with the company, to contact it using a phone number or website you already know is genuine, not the details in the message. Apply the same rule to anyone asking for the list.

Lookalike addresses and false urgency

CISA lists warning signs that fit a wedding setting well: pressure to act immediately, a request for personal information, shortened links you do not recognize, and sender addresses or links that use a subtly wrong spelling of a real company’s name. It also notes that polished grammar no longer proves a message is real, because AI helps scammers write convincingly. Before you send a guest file, compare the sender’s address with the one on your contract, and call the number you already have. Our wedding vendor due diligence checklist explains how to build a trusted contact list in advance.

Edge cases that trip couples up

The default advice covers most situations, and a few families and files do not fit it. These cases come up often enough to plan for.

People and family situations

Guest lists involve relatives with strong opinions and sometimes real safety concerns.

Parents who contribute and want the list

Parents who help pay often expect to see the full list, and refusing outright can feel unkind. You can offer a version that serves the real need. If a parent wants to know how many people are coming, give a count. If a parent wants to suggest invitations for their own friends, give them a separate tab where they add names, and keep your master private. A parent who needs addresses for a mailing can receive only the addresses for the households they are handling. This framing keeps wedding guest spreadsheet permissions about the task, not about trust.

Guests who need extra privacy

Some guests have good reasons not to have an address or phone number circulate, such as someone who has moved to escape a difficult situation. If a guest asks you to be careful, or you suspect a need, keep their details out of every shared file and give vendors only the minimum, such as a name for a place card. You do not need to explain why to the people you are working with. A short line like “this guest’s details are held by the couple only” is enough.

Tool-specific wrinkles

Each platform has details that surprise people, and a few are worth knowing in advance.

Folders and inherited access

Google’s Drive help notes that access inherited from a parent folder cannot be reduced on an individual file, so you have to manage it at the folder level. If your guest sheet lives in a shared “Wedding” folder with a dozen helpers, every one of them may be able to open it no matter how carefully you set the file. Keep the master in a folder only the owners can open. The same help page notes that stopping editors from resharing a file does not cover the parent folder, so a folder editor can still add people. Folders are a common blind spot in wedding guest spreadsheet permissions.

If your list is an Excel workbook stored in OneDrive, Microsoft describes link types that include Anyone, People in your organization, People with existing access, and Specific people. Choose specific people. Microsoft also describes a block-download option, an edit toggle that can be switched off so people can view but not change the file, and password and expiration options that it says require a Microsoft 365 subscription. A copy of the workbook that you email is a different object entirely, with none of those controls, so send a link to the trimmed export, not a file. We did not test these features.

Turnover and handoffs

People join and leave a wedding team. Each change is a moment to adjust access.

Replacing a helper midway

If a helper drops out, remove their access that day, check the register, and ask whether they still hold a copy. If they were an editor, look through version history for changes you do not recognize, remembering that some kinds of changes do not appear there. Then decide whether the replacement needs the same role or a narrower one. This is a good time to ask whether a role that began as editor could now be viewer. Staff changes are when wedding guest spreadsheet permissions are most likely to slip.

A planner who keeps their own files

Planners and venue coordinators often maintain their own copies of guest data in their own tools. Ask which system they use, who in the company can open it, and when they delete it, and put the answers in the contract. If you work with a professional planner, our wedding planning checklist can help you place these questions in the wider timeline. Treat everything a planner says about their own security as their description.

Paper and day-of lists

Not every exposure is digital, and the wedding day has its own versions of the same problem.

Printed lists

A printed guest list left at the venue, in a car, or on a table is a copy no setting can reach. Print only what a person needs, mark it with the person’s job, and collect or shred it afterward. The FTC’s guide for businesses describes a similar idea, advising that records be disposed of in ways that stop them from being read or rebuilt, such as shredding paper. It is written for companies, but the habit transfers.

Day-of staff and arrival lists

Day-of staff such as the check-in table, the shuttle driver, and the coordinator usually need a name and a table or pickup point, not a contact directory. Hand them a trimmed, printed or read-only list, not access to the master file. Our wedding party coordination checklist article lists day-of jobs you can match to these lists, and our guide to wedding guest transportation planning describes what a transport lead actually needs.

If something is exposed

Even careful couples sometimes find a link that was open longer than intended or a file sent to the wrong person. A short plan removes the panic.

The first hour

The first steps are about stopping further spread, not about assigning blame.

Stop the spread

Open the sharing dialog and set general access to Restricted. Google’s help page says that setting general access back to restricted ends link access, and that to remove someone you change their sharing permissions. If the file was published to the web, you must stop publishing it, which is a separate step. If the file was emailed to the wrong person, ask them politely to delete it and to confirm. If a Microsoft link is involved, the Manage access view lets you remove links, and Microsoft notes that links also stop working if the file is moved within your OneDrive. Tight wedding guest spreadsheet permissions make this step quick.

Work out what was exposed

Open the file and ask what was in it at the time. Use version history, within its limits, to see what the sheet contained when the link was open. Make a note of which columns were visible, how many households were affected, and who might have opened it. Write a short, dated note for your own records, because it will help if you decide to tell guests or a vendor.

Telling people and following up

Whether to tell anyone depends on what was in the file, and we cannot give legal advice on notification duties.

Deciding whom to tell

If the exposed information was limited to names and table numbers, a private apology to the helpers may be enough. If it included addresses, phone numbers, or health notes, telling the affected guests directly, with a plain description of what was visible, is kind and often wise. The FTC’s guide for businesses suggests planning ahead for a breach and, for companies, consulting an attorney about notification requirements. If you have a business role, such as running a planning company, look into your legal obligations before deciding.

Reporting and recovery

If you suspect the exposure led to scam messages, the FTC says suspected scams should be reported at ReportFraud.ftc.gov, and that people who shared sensitive information such as a Social Security, credit card, or bank account number can find tailored steps at IdentityTheft.gov. Change the password and check the second-step settings on the account that owned the file, starting with the email address attached to it. Then warn your guests to treat unexpected messages about the wedding with care, pointing them to the contact details they already have.

Closing the sheet after the wedding

The guest list has done its job once the thank-you cards are out, and keeping it open longer than needed is the easiest way to extend your exposure. A planned close-out is the final part of wedding guest spreadsheet permissions.

Remove access in a sensible order

Work from the outside in, so that the largest number of copies stops growing first.

Vendors and day-of staff

Within a few days of the wedding, remove vendors and day-of staff from every file, turn off any link sharing, and ask each vendor who received a guest export to confirm deletion, using the wording you asked for in advance. Update the register with the date removed for each row. Our after-wedding checklist places these steps in the wider list of post-wedding tasks. Ending access is the last step of wedding guest spreadsheet permissions.

Helpers and family

Next, remove helpers and family who had viewer or editor roles, and ask them to delete any downloads. Do this after you have what you need from them, such as final addresses for thank-you cards. If someone is still helping with thank-you cards, keep their access narrow and give it a new end date. Our wedding thank-you cards guide covers the timing.

Decide what to keep

You may want some of the list for years, and you probably do not need all of it.

What is worth keeping

Many couples keep names and addresses for holiday cards and anniversaries, and a record of who attended. If you keep the list, keep a single trimmed copy in a place only you two can open, without dietary or access notes, and without the private comments column. Note the date and review it yearly. Our guide to wedding gift tracking explains what to keep for thank-you purposes.

What to delete, and how

Delete the sensitive columns, the extra exports, and old drafts. Google’s help page notes that if you own a shared file and delete it, people with access may still have copies until you permanently delete it from the trash. So empty the trash after you delete. The FTC’s guide for businesses describes disposal as making data unreadable and unrecoverable, and recommends more than ordinary deletion for drives. For a couple, emptying the trash, deleting downloads, and removing old emails with attachments is a reasonable equivalent, and we did not verify any specific wiping tool. Retiring a list is part of wedding guest spreadsheet permissions too.

Leave the account tidy

The file is gone, but the account that owned it still exists.

Review the account itself

Check the account’s connected apps and signed-in devices and remove anything you no longer use. Confirm that two-step verification is still on, and decide whether the account is a wedding-only address you can retire or a personal address you will keep. If you used a wedding-only address, download what you want to keep before closing it. Our guide to wedding planning website privacy and security covers the website side of the same close-out.

Write down what you did

A short note of what you removed, what you kept, and when will help if a guest ever asks what happened to the list. Store it with your register. It also gives you a ready template for the next family event.

Basics of wedding guest spreadsheet permissions

What is the safest setting for a guest list?

Restricted access, with named people invited by email. Google describes Restricted as the setting where only people who were given access can open the file, so a forwarded link does not help a stranger. Give most helpers viewer access, keep editors to one or two people, and avoid Anyone-with-the-link for a file that holds addresses and health notes.

Can a view-only person still copy my guest list?

Often yes. Google’s help pages say viewers and commenters can download by default unless the owner turns that off, and that view-only users can make a copy of the spreadsheet. Even with those settings off, a person can photograph a screen. Treat viewer as can read, and leave sensitive columns out of any file you share.

Is hiding a column or tab enough?

No. Google’s help page says hiding a sheet is not protection, because anyone with access can unhide it, and that protecting ranges is not a security measure. Delete the columns instead, and share a trimmed copy. If someone only needs counts, send a short message with the number and no file.

Accounts, vendors, and copies

Do I need two-step verification just for a spreadsheet?

Yes, on the account that owns it. Whoever signs in as the owner can change every sharing setting. CISA says multifactor authentication makes accounts much harder to break into and stresses email in particular, so protect the email address attached to the account, then the account itself. A passkey or authenticator app is a good choice.

Should I share my login with my planner?

Try not to. A named invitation gives the planner a separate sign-in and a role you can remove without disturbing anyone else. A shared login gives them your owner powers and leaves no record of who changed what. If a vendor insists, ask for a named user on their side, and change the password afterward.

What do I send a vendor instead of the whole list?

Send only the columns and rows the job needs, as a trimmed copy shared through a named invitation. A caterer needs meal counts and allergy flags, a transport lead needs riders and pickup points, and a printer needs names and mailing addresses. Ask each vendor how long they keep the file and to confirm deletion in writing.

If something goes wrong

Set general access to Restricted right away, check the sharing list, and note which columns were visible. Version history shows edits, but the pages we read do not describe a log of who opened a personal file, so do not assume you can tell. Consider telling affected guests, and be alert for unexpected messages.

When should I close access after the wedding?

Within a few days. Remove vendors and day-of staff first, then helpers and family once you have what you need for thank-you cards. Turn off link sharing, ask vendors to confirm deletion, update your register, and delete extra exports. Empty the trash after deleting, because Google notes people may keep copies until the file is permanently removed.

Your next steps

This week

Look at the sharing dialog

Open your guest list, click Share, and read the general access line. If it says anything other than Restricted, change it, then review the list of people. Remove anyone who no longer needs access and lower editors to viewers where you can. This single check handles the biggest risk in wedding guest spreadsheet permissions, and it takes about five minutes. Add the habit to your broader plan using our wedding planning checklist.

Protect the owner account

Make sure the account that owns the sheet, and the email address behind it, have a long unique password and two-step verification. Add a second method for your partner and store printed backup codes where you can both find them.

This month

Sort the columns and split the file

Triage your columns into helper-visible, need-to-know, and couple-only. Move couple-only columns into a separate tab or file, and create trimmed exports for each vendor. Our wedding RSVP data export guide helps you decide what your website collects in the first place.

Start the register

Create the access register in a file only the two of you can open. Record each person, their role, their job, and an end date. Pick a monthly review date and put it on your calendar.

Before and after the wedding

Review the week before

In the final week, confirm that no guest file is set to anyone with the link. Give day-of staff a printed or read-only list, not access. Confirm every vendor’s final export is the latest version, and retire older ones.

Close access afterward

Within a few days, remove vendors and helpers, turn off link sharing, ask for deletion confirmations, delete extra exports and empty the trash. Keep one trimmed copy if you wish, and write down what you did. For the broader plan, see our wedding planning guide and our guide to wedding planning password sharing.

Sources & methodology

How we built this guide

What we relied on

This guide to wedding guest spreadsheet permissions draws on U.S. federal consumer and business guidance, a national standards body, the Cybersecurity and Infrastructure Security Agency, the World Wide Web Consortium, and help pages published by Google and Microsoft. Statements about what a product does are attributed to the company that published the page and treated as that company’s description, not independent testing. The three-level column triage, the permission matrix, the register, and the export procedure are our own editorial constructions, not requirements from any standard, and the time estimates are our own rough guesses. We read these pages on November 12, 2026. Some pages did not load, so we only state what a page we read said, and menus and settings change, so confirm what you see in your own account.

What we did not do

We did not test any spreadsheet product, add-on, or vendor, and we did not verify current pricing or plan contents. We did not give legal, privacy-compliance, or security advice, and nothing here tells you what the law requires for your situation. Privacy rules differ by state and country.

Source list

Government and standards sources

Product help pages (vendor descriptions, not tested)

You may also like