A Note on Figma Access  🔗 **Source:** [A Note on Figma Access](https://make.wordpress.org/design/2026/09/18/a-note-on-figma-access/) > [!note]+ Document Notes > tags: [wordpress-design, figma-access, design-tooling, penpot, contributor-permissions] > author: Joen Asmussen > source: Make WordPress Design > reference: https://make.wordpress.org/design/2026/09/18/a-note-on-figma-access/ > date created: 2026-09-29 15:55 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: A Note on Figma access > <!-- deep-read:sections start --> ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor appendix](#-refactor-appendix--a-note-on-figma-access) ## 📝 Summary - **Source type.** This is a short process notice from the WordPress Design team, published on the Make WordPress Design blog on 2026-09-18 by Joen Asmussen. It is first-party guidance about a team tool, about 235 words in the captured text. It is neither opinion nor vendor marketing, though it names a commercial interest: Automattic pays for the Figma seats (¶0). - **What happened.** The notice explains who gets Figma edit access for WordPress project mockups, why edit seats are scarce, and two habits that keep them scarce: how "anyone can edit" links behave (¶3) and a reminder to downgrade approved access after a month (¶4). - **The claim.** Figma is free to sign up for and free for creating and editing drafts, so Automattic sponsors access for a subset of contributors (¶0). Edit access is limited to a few paid seats because each seat is a recurring monthly fee and needs manual approval and manual downgrading (¶1). - **The mechanism.** A shared link set to "anyone can edit" turns every click into a request for recurring edit access. Figma admins get a notice, can't tell why the access is needed, and often deny it (¶3). Workspace admins who approve access should set a reminder to downgrade it to "view" a month later, because the access continues until someone changes it (¶4). - **Why it matters.** Seat approvals are manual work for admins and a paid cost for the sponsor. A link setting that creates request noise wastes both. The notice also says downgrading is not destructive, since files can be duplicated to a personal account (¶4). - **Key stakeholders.** Current Figma edit-access holders, Figma workspace admins, the Design team, the sponsor Automattic, and anyone who shares or opens Figma links. The #design Slack channel is the named discussion venue (¶3, ¶6). The post carries Meta and Community team tags (¶7). - **Risks and tradeoffs.** The one-month downgrade depends on an admin remembering (¶4). Edit access remains capped by budget. Penpot appears as a possible alternative, but the text gives no proposal details, owner or timeline (¶6). - **Bottom line.** The actionable content is two rules: don't share "anyone can edit" links, and downgrade approved access after a month. The notice gives no seat counts or cost, so scale is unknown from this source. ## 📖 Main content **The core argument.** Figma is the working tool for WordPress mockups, and sign-up and draft editing cost nothing. Paid edit seats cost money and admin time, so they stay few (¶0, ¶1). The rest of the notice tells seat holders and admins how to avoid consuming seats by accident. **Two behaviors to change (¶3, ¶4).** 1. **Link sharing.** Setting a shared link to "anyone can edit" means each person who clicks it requests recurring edit access. Admins can't see a reason with the request, so denial is common. The notice says to raise real access needs in #design first (¶3). 2. **Downgrade discipline.** Admins who approved edit access should schedule a reminder to set it to "view" one month later, since it otherwise continues. The notice states downgrading is not destructive and files can be duplicated to a personal account (¶4). **What comes next (¶5, ¶6).** Proposals to consider Penpot as an alternative to Figma have appeared in #design, and readers are invited to comment there (¶6). Courtney's vault already tracks Penpot in several notes (for example `_Synthesis Backlog.md`), so this notice is a project-side data point for that thread. The text says nothing about what those proposals contain. **Contested or unverified in this source.** - "Free to sign up for" and free draft editing (¶0) match what the linked Figma home page would document, but the captured text doesn't quote pricing terms. - The number of sponsored seats, the monthly cost and the count of approved or denied requests are not stated. - Who counts as a "subset of contributors" (¶0) isn't defined in the notice. The one link on "Edit access is limited to only a few paid seats" goes to the Design handbook Figma page, which likely holds the process. - The Penpot proposals have no link, so their status is unknown from the capture. ## 🗒️ Notes #### 📄 ¶0-¶1 Why edit access is limited - Figma builds and maintains mockups for WordPress. Sign-up and draft editing are free. - Automattic sponsors access for a subset of contributors. - Edit access is capped at a few paid seats: a monthly recurring fee plus manual approval and manual downgrading. #### 📄 ¶2-¶3 Guidance for current edit holders - The section heading is "A note on granting edit access" (¶2). - An "anyone can edit" link makes every clicker a requester for recurring edit access. - Admins see a request notice without the reason, so requests are often denied. Discuss actual access in #design first. #### 📄 ¶4 Guidance for Figma workspace admins - Set a reminder to downgrade approved access to "view" after a month. - Without a manual downgrade, edit access continues. - Downgrading doesn't delete work: files can be duplicated to a personal account. #### 📄 ¶5-¶6 What's next - The "Next" heading (¶5) introduces one item. - Penpot has been proposed as an alternative to Figma in #design. Readers are asked to share thoughts there. #### 📄 ¶7-¶8 Tags and comment prompt - The tag line lists two team blogs, Meta and Community (¶7). - "Login to Reply" is the comment form prompt, so replying needs a WordPress.org login (¶8). ## 📚 References Checked against the captured link list, which has 5 entries (4 distinct URLs): - [Figma](https://www.figma.com/), linked from "Figma" in ¶0. - [Design handbook, Tools: Figma, Getting started](https://make.wordpress.org/design/handbook/get-involved/tools-figma/#getting-started), linked from "Edit access is limited to only a few paid seats" in ¶1. This is the primary source for the access process. The captured text doesn't reproduce it. - [#design on WordPress Slack](https://wordpress.slack.com/archives/C02S78ZAL), linked twice from "#design" (¶3 and ¶6). Slack sign-in is required. - [Comment form login](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdesign%2F2026%2F09%2F18%2Fa-note-on-figma-access%2F%23respond&#038;locale=en_US), linked from "Login to Reply" (¶8). - The tag line in ¶7 lists [Meta](https://make.wordpress.org/meta/) and [Community](https://make.wordpress.org/community/) as text, with no link entries in the captured list. Claims with no link in the captured markup: Automattic's sponsorship (¶0), the manual-approval process description beyond the handbook link (¶1), and the Penpot proposals (¶6). ## 🗣️ Paraphrase WordPress designers use Figma for project mockups. Signing up and editing drafts is free, and Automattic pays for a limited number of edit seats for some contributors. Each edit seat costs a monthly fee, and admins have to approve it by hand and downgrade it by hand later, so the seats are few. If you hold edit access, don't share a link set to "anyone can edit." Everyone who opens it asks for recurring edit access, admins can't see why, and most of those requests get denied. Ask in the #design Slack channel first. If you're a Figma workspace admin who approved someone, set a reminder to switch them to "view" a month later, because the access won't end on its own. Switching to "view" keeps their work available: they can duplicate any file to a personal account. Some people have suggested Penpot as an alternative to Figma. The Design team asks for thoughts in #design. ## 📰 Newsletter **Sharing a Figma link? Check the setting first.** The WordPress Design team posted a short reminder about Figma edit access. Figma is free to sign up for and free for drafts, but edit seats are paid, and Automattic sponsors them for a subset of contributors. An "anyone can edit" link makes every visitor a request for recurring edit access, and admins usually deny those because no reason comes with them. Two takeaways: ask in #design before you need edit access, and if you approve access as a workspace admin, set a one-month reminder to downgrade it to "view." Downgrading doesn't destroy work, since files can be duplicated to a personal account. The note also says people have floated Penpot as an alternative to Figma in #design, so that's the place to weigh in. Links: [the notice](https://make.wordpress.org/design/2026/09/18/a-note-on-figma-access/), [Design handbook Figma page](https://make.wordpress.org/design/handbook/get-involved/tools-figma/#getting-started), [Make Design](https://make.wordpress.org/design/). ## ✅ Action items #### DevRel - Developer advocacy: no action from this source. - Education: no action from this source. - Developer experience: no action from this source; nearest relevance is the "share links safely" habit for any shared design file used in demos. - Developer marketing: no action from this source. - Community management: no action from this source. - Internal/external: no cross-project action from this source. #### OSPO - Policy and governance: the notice sets a de facto access policy (few paid seats, manual approval, one-month downgrade). Confirm it is written in the Design handbook page linked from ¶1. - License compliance: no action from this source. - Security management: the "anyone can edit" link behavior is an access-control risk as well as a cost issue. No action from this source beyond noting it. - Software inventory: no direct action; Figma (paid, sponsored) and Penpot (proposed) are tool inventory entries for the project. - Developer support: no action from this source. - Community engagement: no action from this source; the sponsor relationship (Automattic and Figma seats) is a candidate for a public sponsorship ledger entry. - Strategic alignment: no action from this source. #### Community - Maintainers: no action from this source. - Contributors: contributors with edit access should check their shared Figma links for "anyone can edit" and raise real access needs in #design first (¶3). - Sponsors: Automattic sponsors the seats (¶0). Ask whether seat count and cost can be published, since the notice gives neither. - Ecosystem: no action from this source. #### WordPress - Core: no action from this source. - Core Performance: no action from this source. - Core AI: no action from this source. - **Core Program Team:** no action from this source. - Mobile: no action from this source. - Playground: no action from this source. - Community: the post carries a Community team tag (¶7). Tell Contributor Day and WordCamp organizers who run design sessions to use "view" links, and to send edit requests to #design. - Training: no action from this source; if a design contribution lesson exists, add the "don't share anyone-can-edit links" rule. - Marketing: no action from this source. - Support: no action from this source. - Design: (1) Audit shared Figma links for the "anyone can edit" setting and switch them to a narrower setting. (2) Workspace admins add a one-month calendar reminder for each approved edit grant (¶4). (3) Record current seat count, cost and denied-request volume so the Penpot discussion has numbers (¶6). (4) Answer in #design on Penpot. - Documentation: confirm the Design handbook Figma page (linked from ¶1) states the link-sharing and downgrade rules from ¶3 and ¶4. - Photos: no action from this source. - TV: no action from this source. - Polyglots: no action from this source; the notice is English text on a Make blog. - Accessibility: no direct action from this source. If Penpot evaluation proceeds, ask that keyboard and screen reader support of the candidate tools be part of the comparison. - Meta: the post carries a Meta team tag (¶7). Check that Figma-related access requests don't depend on Meta-owned tooling, and whether a WordPress.org-side notice or form for requests would help. - CLI: no action from this source. - Hosting: no action from this source. - Tide: no action from this source. - Openverse: no action from this source. - Themes: no action from this source. - Plugins: no action from this source. #### The WPOCC - Programs: no direct action; if The WP Open Community Collective ever funds contributor tooling seats, this notice shows the cost pattern (recurring fee plus manual admin time). - Projects: no action from this source. - Funding experiments: no action from this source. ### FAIR - Technical independence: no direct action; the Penpot proposal (¶6) touches tool dependence on a single vendor, which is the same independence question at the design-tool layer. - Policies and covenants: no action from this source. - Productized governance artifacts: no action from this source. ## 🧪 Hypotheses 1. Most denied Figma edit requests come from "anyone can edit" links rather than from deliberate access requests. 2. Adding a one-month downgrade reminder for approved edit grants lowers the number of active paid seats compared with grants that have no reminder. 3. Posting the seat cap and access process in the handbook reduces edit-access requests that have no stated reason. 4. Contributors who need only to comment or review are served by "view" access and don't need an edit seat. 5. A tool with no per-seat edit fee would remove the admin approval work described in ¶1. ## 📊 Methodology - **H1.** Ask Figma admins to export the request log for one quarter and label each request by origin: shared-link click or direct ask. Compare denial rates between the two. - **H2.** Compare the count of edit seats in use over 90 days for grants made before and after the reminder practice, using the admin panel's seat report. - **H3.** Count requests without a stated reason in the 60 days before and after the handbook change. Track #design messages that begin with a stated need. - **H4.** Survey current seat holders on what work they did in the last 30 days (edit, comment, view) to see how many edit seats sit unused. - **H5.** Model the admin time per approval and per downgrade from admin interviews, then compare it with the time cost for a candidate tool. This gives a number for ¶1's "manual approval" cost. - **Controls.** Separate one-off design sprints from steady contributors, and state the period, since project mockup work is uneven. ## ❓ Questions - How many sponsored seats exist, and what does each cost per month? The notice gives neither (¶0, ¶1). - Who decides which contributors count as the "subset" (¶0)? - What happens to a denied "anyone can edit" requester's access request? Does it expire? - Who owns the one-month downgrade reminder if the approving admin changes roles (¶4)? - What do the Penpot proposals cover: hosting, cost, file migration, plugin support (¶6)? - Is there a way to make links comment-only or view-only by default so the "anyone can edit" case can't occur? - Does the Design handbook page linked from ¶1 already say what the notice says? - Would an open-source tool fit the project's contributor accessibility and localization needs better than Figma? ## 🔮 Future research - **Tool cost per contributor.** No figure in the source ties seat cost to design output. A per-seat cost and mockups-shipped comparison would inform the Figma versus Penpot thread. - **Access lifecycle data.** How long approved edit grants stay active without a downgrade is unmeasured here. A 6-month lookback on the admin log would show it. - **Open-source design tool fit.** Compare Penpot and Figma on file portability, export formats, plugin ecosystems and keyboard accessibility for project contributors. - **Sponsor dependency.** A single sponsor pays for the seats. Documenting what happens if sponsorship ends would show the project's exposure. - **Contributor experience.** Interview design contributors who were denied access to learn what they did next. ## 💡 Implications - **Practice.** Design contributors can use "view" or comment links by default and ask in #design for edit access with a stated reason. Admins can add a downgrade reminder at approval time. - **Policy.** The notice is a lightweight access policy that lives in a blog post and a handbook page. Written seat rules and a named reviewer role would make it auditable. - **Security.** "Anyone can edit" on a shared design file lets any link holder request write access to project files. The notice frames it as a cost issue. It is also a permissions-hygiene issue. - **Education.** New design contributors learn the link-sharing rule and the free draft path, so a first contribution doesn't require an approved seat. - **Funding.** Sponsored seats are an in-kind contribution from Automattic. The Penpot proposal (¶6) suggests the project is weighing dependence on a paid, sponsor-funded vendor tool against an alternative. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level about 9 and Flesch Reading Ease about 60, computed with a quick script over 235 words (14 sentence units) of the cleaned text. The tiny sample makes the numbers rough. Terms like "workspace admin," "seat" and "downgrade to view" carry the difficulty. #### 👀 Visual learners - Present: no images, screenshots or diagrams appear in the captured text. - Improve: add a screenshot of Figma's share dialog with the "anyone can edit" setting marked, plus the setting to use instead, with alt text. #### 🔊 Aural learners - Present: no audio or video referenced in the captured text. - Improve: for a notice this short, a text-only post is fine. A 60-second screen recording of changing the link setting would help admins who learn by listening. #### 🗣️ Verbal learners - Present: plain sentences explain the reason (recurring fee, manual approval and downgrading) before the rule (¶1, ¶3). - Improve: define "seat," "edit access" and "view" on first use, and name where the request notice appears for admins. #### 🧩 Kinesthetic learners - Present: two concrete actions: change link sharing, set a reminder to downgrade (¶3, ¶4). - Improve: add click-by-click steps for changing a link's permission and for downgrading a member to "view" in Figma. #### 🧠 Logical learners - Present: the cost-to-rule chain is stated: paid seat, manual work, so limited access (¶1). - Improve: a small table of access type, cost, who approves, and default duration would compress ¶0 to ¶4. #### 🧑‍🤝‍🧑 Social learners - Present: #design is named twice as the place to discuss access and Penpot (¶3, ¶6). - Improve: add a named admin or role to contact, and a monthly office-hours slot for access questions. #### 🧘‍♀️ Solitary learners - Present: the handbook link lets a reader check the process alone (¶1). - Improve: add a checklist ("Is my link set to view? Is my access still needed?"). #### 🌿 Naturalistic learners - Present: no natural-world content. - Improve: no natural fit. Skip rather than force one. ## 📊 Accessibility assessment #### Screen reader semantics - Present: the captured text shows two short labels, "A note on granting edit access" (¶2) and "Next" (¶5), that read as section headings. The capture doesn't show whether they are real heading elements. Link text is descriptive for the handbook and Figma links ("Edit access is limited to only a few paid seats" is a long link label but says where it goes). - Improve: confirm the two labels are heading elements (WCAG 1.3.1, 2.4.6). "Next" is a vague heading, so "Next steps: Penpot" would tell a screen reader user more (2.4.6). "#design" appears as link text twice, going to the same Slack channel, which is consistent (2.4.4). #### Keyboard navigation - Present: nothing to judge from the captured text. The Make sites are standard WordPress themes, but this capture doesn't show focus behavior. - Improve: the Slack link needs a Slack account and the comment form needs WordPress.org login. Both are a barrier to anyone without an account, and the notice doesn't offer an alternative route. #### Contrast and readability - Present: unknowable from cleaned text. The paragraphs are short. - Improve: none supportable from this capture. Contrast (1.4.3) depends on the theme. #### Text resizing and reflow - Present: a text-only post with no tables or images reflows by default on a standard theme. - Improve: none needed from the capture (1.4.4, 1.4.10). #### Media and captions - Present: no media referenced in the captured text. - Improve: if a screen recording of the Figma steps is added, it needs captions and a transcript (1.2.1, 1.2.2). #### Forms and interactions - Present: a comment form behind "Login to Reply" (¶8). - Improve: the notice asks for feedback in Slack (¶3, ¶6) and doesn't mention the form as a route. State that comments below are also read (3.3.2 covers label clarity on the form itself, which the capture doesn't show). #### Standards reference - Gaps against WCAG 2.2 AA that the capture supports: **1.3.1** (heading elements unverifiable), **2.4.6** ("Next" is a weak heading). Screenshots, if added, need **1.1.1** alt text. The larger accessibility question is outside the text: whether Figma (and a possible Penpot replacement) is usable with a keyboard and screen reader for contributors who use assistive technology. ## 🌍 DEIB assessment #### Cultural breadth - Present: Figma is a global tool, and the guidance is portable across regions. - Improve: the notice is English-only and points to an English-language Slack channel. State whether time zones affect the one-month downgrade window and how contributors outside the sponsor's region request access. #### Inclusive language - Present: plain language, second person for both holders and admins ("If you currently have edit access", "If you are a Figma workspace admin"), and reassurance that downgrading "is not destructive" (¶4). - Improve: "seats," "downgrade" and "view" are undefined. "Hard to know why that access is needed" (¶3) explains denials without blame. #### Neurodiversity support - Present: short paragraphs, one instruction per audience, and two labeled sections. - Improve: add a bulleted "Do this" list and put the two rules first, so a skim reader finds them without reading the sponsor background. #### Representation - Present: the post is signed by a named author and addressed to admins and holders alike. - Improve: no contributor voice appears. If Penpot is discussed, include design contributors who are not seat holders, since they are most affected by the cap. #### Psychological safety - Present: the tone avoids blame. Denials are explained as a signal problem, not a contributor problem (¶3), and downgrading is framed as reversible-safe (¶4). - Improve: say that asking for edit access is welcome and state expected response time, so contributors don't read the cap as a barrier to joining. ## ✅ Logical validity #### Strong reasoning - **Causal, ¶1 to ¶3.** Recurring fee plus manual work explains the cap, and the same manual work explains why anonymous access requests get denied. The chain is short and each step is stated. - **Mechanism, ¶3.** The claim that an "anyone can edit" link produces access requests from every clicker follows from how the setting works and is easy for a reader to check in Figma. - **Risk reassurance, ¶4.** Stating that downgrading is not destructive and naming the escape (duplicate to a personal account) answers the obvious objection to downgrading. #### Fallacies - No formal fallacy found. I checked each claim in ¶0, ¶1, ¶3, ¶4 and ¶6 for unsupported generalization, false dichotomy and appeal to authority. - **Unquantified claim, ¶1.** "Only a few paid seats" gives no count. Fix: state the number and monthly cost, or link the handbook figure. - **Unsupported frequency, ¶3.** "It is often denied" gives no rate. Fix: give the denial share for one period. - **Vague scope, ¶0.** "A subset of contributors" doesn't say how the subset is chosen. Fix: link the eligibility rule. #### Tone of voice - Informative and courteous, in second person with a conditional structure ("If you currently have edit access," "If you are a Figma workspace admin"). The notice avoids blame and includes one soft invitation ("Feel free to share your thoughts there," ¶6). Evaluative words are rare: "Importantly" (¶4) is the only emphasis marker. ## 🛡️ DARVO analysis Not applicable to this source. DARVO (Deny, Attack, Reverse Victim and Offender) describes a response pattern to accusation, and this is a procedural notice with no accusation or accuser. For completeness across the three prongs: **Deny**: nothing is denied, and the cost and manual-work limits are stated openly (¶1). **Attack**: no person, tool or team is criticized. Figma and Penpot are named without disparagement (¶0, ¶6). **Reverse victim/offender**: no such move appears. ## 🎯 Conclusion The Design team's notice explains why Figma edit access is scarce (a recurring fee plus manual approval and downgrading, with Automattic sponsoring seats) and gives two rules: don't share "anyone can edit" links, and downgrade approved access to "view" after a month (¶0, ¶1, ¶3, ¶4). It also flags Penpot as a topic for #design (¶6). The text gives no seat count, cost or Penpot proposal details. **Next steps for readers:** if you hold edit access, check your shared links and raise real needs in #design first. If you're a Figma workspace admin, set the one-month downgrade reminder at approval time. If you follow open-source tooling questions, watch #design for the Penpot discussion and bring seat and cost data to it. ## 🔄 Refactor Appendix — A Note on Figma access > Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 4 Literature, 1 Permanent. Resonance filter applied: the sponsor and Penpot lines > were kept in the notes and references only. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] Paid Figma seats stay scarce by design > [!quote] [¶1] > Edit access is limited to only a few paid seats, because it is both a recurring monthly fee **Context & use**: - ¶1, the reason for the cap. The rest of the sentence adds the manual approval and downgrading burden. - It ties tool access to recurring cost and admin time. It also frames the sponsor's role (¶0). **Tags**: #xref #addendum <!-- atomicity: 1 idea ✓ --> #### [H2] Anyone-can-edit links request recurring edit access > [!quote] [¶3] > anyone who clicks the shared link will be requesting recurring edit access whether they need it or not. **Context & use**: - ¶3, the mechanism behind request noise and denials. - A permissions-hygiene rule that applies to any shared design or document link. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H3] Edit access persists until an admin downgrades it > [!quote] [¶4] > Unless manually downgraded, it will continue. **Context & use**: - ¶4, the reason for the one-month reminder. - A default-persists pattern: access that needs manual removal drifts upward without a scheduled review. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> #### [H4] Downgrading access keeps the work > [!quote] [¶4] > being downgraded to “view” is not destructive: you can still duplicate any file(s) you’ve been working on to your personal account. **Context & use**: - ¶4, the reassurance that removes the main objection to downgrading. - It gives admins wording they can reuse when they downgrade someone. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] Access that needs manual removal needs a scheduled removal **Claim** (one sentence, Courtney's voice): If turning off access takes a manual step, set the date for that step when you grant the access. **Evidence pointer**: [[#H3]] · [[#H2]] **Scope & conditions**: Holds for paid or sensitive access with no expiry setting in the tool, as with the Figma edit seats in the notice. It's unnecessary where the tool expires access on its own. The notice shows no data on how often the reminder is missed. **Links**: - [[Access review and least privilege]] — because extends - [[Tool lock-in and portability]] — because contrasts on where control sits, with the tool's expiry setting versus an admin's reminder - [[Contributor onboarding friction]] — because applies-in granting contributor tool access <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Find out how many sponsored Figma seats exist and what they cost: https://make.wordpress.org/design/handbook/get-involved/tools-figma/#getting-started #fleeting #inbox - [F2] Open question: what do the Penpot proposals in #design actually cover, and how does that compare with what the vault already tracks on Penpot? #fleeting #inbox - [F3] Article seed: "Set the removal date when you grant access" as a rule for contributor tooling #fleeting #inbox #articleseed - [F4] Check my own Figma and Google Drive shared links for "anyone can edit" settings #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Read the Design handbook Figma page and note seat count, cost and downgrade rule, WordPress design tooling #things - [ ] Read the #design Penpot thread and link it to the vault's Penpot notes, WordPress design tooling #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/A Note on Figma Access.md|A Note on Figma Access by Joen Asmussen]] ## Highlights - Edit access is limited to only a few paid seats, because it is both a recurring monthly fee, but also one that requires manual approval and subsequent manual downgrading when access is no longer needed. ([View Highlight](https://read.readwise.io/read/01m3qc0xfmv8xz89q2r7wng9f9)) - Note: [H1] Paid Figma seats stay scarce by design - Tags: atom/literature/h1 - If you currently have edit access, you should be aware that sharing a link with “anyone can edit” access means that anyone who clicks the shared link will be requesting recurring edit access whether they need it or not. Figma admins will receive a notice of requested access, but it’s hard to know why that access is needed, which is why it is often denied, and actual access is best discussed in the #design channel first. ([View Highlight](https://read.readwise.io/read/01m3qc1010a7fkr20pfqhgekbj)) - Note: [H2] Anyone-can-edit links request recurring edit access - Tags: atom/literature/h2 - If you are a Figma workspace admin and approved Figma access, please set a reminder to downgrade that access to “view” a month later. Unless manually downgraded, it will continue. Importantly, being downgraded to “view” is not destructive: you can still duplicate any file(s) you’ve been working on to your personal account. ([View Highlight](https://read.readwise.io/read/01m3qc126y0m6ec02azq41dcza)) - Note: [H3] Edit access persists until an admin downgrades it - Tags: atom/literature/h3