Chapter 13: Properties, filters and permissions

What this chapter covers

On GitHub’s website, the facts about an issue or a repository are spread over a page, with the controls to change them tucked into menus and side panels. In the Workbench, everything about one thing is on one sheet, and the sheet is where you change it. This chapter is about that sheet, and about the two questions that come with changing things: which ones, and am I allowed?

You open a Properties sheet and change a field, change many things at once, say a change in words, undo a change, and filter and shape a list. Then you look at permissions: what you are allowed to do, how to get what you are missing, what the Workbench itself allows each account, and who else has access and why.

By the end you will be able to change anything the Workbench shows, safely, and answer “why can’t I?” and “who can?” without leaving the window.

Properties: Alt+Enter on anything

Select a row in the list and press Alt+Enter. A Properties sheet opens for it: an issue, a pull request, a repository, a label, a milestone, a branch, a release, a workflow run, a person, a team, a gist, an alert, and the rest. Item > Properties… and the last row of every context menu open the same sheet. In the tree, Alt+Enter on a repository opens the repository’s own sheet.

The sheet is a set of pages. The first is always General.

The sheet remembers the page you used last for each kind of thing. If you set milestones all morning, the next issue’s sheet opens on Organize.

Changing things

A field you are allowed to change is an ordinary control. A field you are not allowed to change is read-only, and the line under it says why, for example “changing this needs triage access to owner/name; you have read access”, and who can change that. F1 on the field says the same.

The context menu of an issue or pull request still names the common changes: Edit Title…, Labels…, Assignees…, Milestone… and Projects… open the sheet with focus already on that field. There are no separate keys for single properties: Alt+Enter, then the page.

You: your own relationships

Anything you can have a relationship with has a You page, right after General: the second page, so Ctrl+2 reaches it. It holds every relationship GitHub offers with that thing, each as a control you change like any other field, and saving sends only the ones you changed and says what happened in one sentence: “owner/name: starred on; watch level all activity.”

Some relationships GitHub’s API cannot change, and those are read-only boxes whose F1 says why in one sentence: whether something is Pinned to your profile (customize your pins on your GitHub profile page), whether you are Sponsoring someone (that spends money at a tier you choose, so it is done from their Sponsor node, never a check box), whether a pull request or a discussion is pinned (GitHub pins only issues through its API), and whether somebody follows you, which is theirs to change. The menu rows you already know, such as Star or Unstar, Watch or Unwatch, Follow or Unfollow, React… and Pin or Unpin Issue, send the same requests as the You page. Read Only and Safe Mode lock the You page like every other page, with the reason under each field.

The rest of the relationships, and every one as a row on the context menu too, each saying its outcome in one sentence:

Saving safely

Many at once

Select several rows (Shift and Ctrl with the arrows, or Ctrl+A) and press Alt+Enter. One sheet opens for all of them, titled “Properties of 5 issues”.

Batches pause a second between items, because GitHub limits how quickly one account may make changes.

Saying it in words

Tools > Plain-Language Batch… (Ctrl+Shift+S) takes the change as a sentence, for the repository you are in:

There is no AI in it. QUILL reads a fixed set of words: labelled, without label, with no label, by, assigned to, unassigned, in milestone, waiting on me, mentioning me, open or closed, an age (“older than 90 days”, “updated before March 2024”), and oldest or newest first. The same sentence always means the same thing, and a word it does not know is never guessed: it says what it does read, and gives you your sentence back to correct.

It then searches GitHub and shows every item it found as a checked list. Uncheck any you want left alone, and OK goes on to the same preview and results as any batch above: “Change 12 issues: state to closed as completed.” Closing as a duplicate is not a batch, because each one needs the issue it duplicates; close those one at a time with Delete on the row. The WordPress Workbench’s Plain-Language Batch reads ages the same way.

Undoing a change

Ctrl+Z in the list or the tree undoes your last change on GitHub, where GitHub allows it, and Ctrl+Y makes it again. In a text box they undo and redo your typing as usual. The same commands are Edit > Undo GitHub Change and Redo GitHub Change.

Undo reads the object from GitHub first, so a milestone goes back as the milestone it was and a ruleset keeps its other rules. If somebody changed the field since, Undo stops and says so rather than overwrite them. A redone change can be undone again. A change GitHub cannot reverse says why in its preview, before you save it, and again if you ask to undo it: a secret’s old value is never given back, and taking an item out of a Project deletes its field values there.

Account > Change History… (Ctrl+Shift+H) lists every change the Workbench has made, newest first: what, when, before and after, and whether GitHub confirmed it. Undo This Change reverses the selected one. You can save the list as a CSV file or clear it. It stays on this computer for 90 days, and a secret’s value is never in it.

Account > Set Your Status… (Ctrl+Alt+S) reads your GitHub status, the short message beside your name, and offers to set a new one or clear it. A new one asks, a question at a time, for the message (“Back Monday”), an emoji by its GitHub name (palm_tree, house, or none), whether to mark yourself busy, which tells people asking for your review that you may answer slowly, and when it clears itself: never, in 30 minutes, an hour, four hours, tomorrow or in a week. You hear the status as it is now.

Filtering

The filter box (Ctrl+E) takes plain words, which narrow the loaded list, and GitHub’s own search terms such as label:bug or no:milestone, which ask GitHub. Three other ways write into the same box.

Has Conflicts is the one GitHub’s search cannot answer, so the Workbench checks the pull requests already loaded and the Items cell of the status bar says so. View > Load All (Ctrl+Shift+Page Down) loads every page to be sure.

Filtering every other list

Branches, tags, commits, releases, workflows, runs and the other lists are read whole, so the words before a colon are checked here, over the rows already loaded. Each list answers its own:

A name takes * as a pattern (name:release-*). A minus in front leaves those out (-conclusion:success). Numbers and dates take >, <, >=, <= and a range with two dots (ahead:>=3, created:2026-01..2026-06); a date can be just a year or a month. no:repo keeps the rows with none. The Items cell of the status bar says how many the filter kept of how many loaded, such as “Filtered here: 2 of 3 loaded. Load All to be sure.”, and names any word this list cannot filter on, so nothing is quietly ignored.

The Search place’s lists send the whole box to GitHub instead, so there GitHub’s own search terms work: language: and stars: for repositories, committer: for commits, location: for people.

More rows

Every list starts with one page: 30 issues or pull requests, 50 rows of anything else. Load More (Alt+Page Down) reads one page more each time, and Load All (Ctrl+Shift+Page Down) reads up to a thousand at once. Both work on every list in the Workbench, Notifications, My Work, discussions, labels and the merge queue included. When a list holds only part of what GitHub has, the Items cell of the status bar says so, for example “Gists: showing the first 50 items; more may exist. Load More or Load All reads the rest.”, so a short list is never mistaken for the whole of it.

Shaping the list

Permissions

Yours

Account > GitHub Permissions… (Ctrl+Shift+P) lists every permission the Workbench can use, what it unlocks, and whether you have it, such as “project: set an item’s projects and edit project fields. You do not have it.”

A fine-grained token does not tell anyone its permissions, so for one of those the list says “This token’s permissions are set on GitHub” rather than guessing.

Read Only, Organize or Full

Account > Roles and Access > Workbench Level for This Account… sets what the Workbench may change with an account, whatever GitHub would allow. Read Only changes nothing, which suits demonstrating or looking around someone else’s organization. Organize allows organizing and comments, such as labels, assignees, reactions and closing issues, but not access, settings or deleting. Full allows everything your access allows. Safe Mode makes every account Read Only.

Every change is checked against the level once, before anything is sent, whether it comes from a menu row, a sheet, a batch, F11 or the API Console. A change the level does not allow is refused in one sentence naming the level it needs: “Cannot delete the label: it needs Full in the Workbench, and this account is Organize; Account, Roles and Access, Workbench Level for This Account changes it.” On a sheet, the reason is beside each locked field. Alt+5 says what you can do where you are.

The smallest permissions that would do

Account > Roles and Access > Least Privilege Advice… is a report: it changes no token and no setting. It is based on what the Workbench saw this account do on this computer: the kinds of request it sent (never which repository or person), the changes that passed the Workbench level check and how far each reached, Change History, the scopes GitHub names for a classic token, and every time GitHub refused a request and said which permission it wanted. From those it suggests:

It then says what it cannot know. It saw only this computer’s use, not another computer, the gh command or GitHub’s website. GitHub does not list a fine-grained token’s exact permissions, so the report can say only what worked and what was refused. And it cannot tell whether a repository is private, so repo is suggested only where that would matter. To change a token, use GitHub’s Settings, Developer settings.

Who else has access

A repository’s sheet has an Access page: the people with access, the teams, and pending invitations. Select a row and use Add…, Change… or Remove (Insert, F2 and Delete work too). Each change is read back to you first, and recorded in Change History. The Workbench refuses to remove your own admin access or the last owner, and says who else could do it. Organization and team sheets work the same way for members and maintainers.

On an organization’s sheet, each member reads with their role and whether two-factor sign-in is on: “kim, person, member, direct, two-factor off”. GitHub shows two-factor only to owners; anyone else hears “two-factor not shown to you”. Change… on a member offers member, owner, or outside collaborator; making someone an outside collaborator takes them out of the organization and its teams and leaves only the repositories they were given directly, so QUILL asks you to type their name first. On the Outside Collaborators page, Add makes a member an outside collaborator, Change… invites one to be a member, and Remove takes away every repository they have here, again after their name is typed. You cannot make yourself an outside collaborator, remove yourself while you are the last owner, or remove the last owner.

A team’s sheet lists its maintainers and members, and its Repositories page lists every repository the team reaches with its role there. Add gives the team a repository, Change… changes its role, and Remove takes it away. The last maintainer cannot remove themselves. When you take admin away from a team you are on, QUILL asks GitHub first whether that team is how you administer the repository, and if it is, says so and changes nothing. The General page’s Parent team moves the team under another (empty makes it a top-level team), and New Team… on an organization asks for the parent and whether mentions notify the team.

The organization’s Members list in the tree reads the same way (“kim, member, two-factor off.”), and Delete there asks for the name typed and keeps the last owner. Members Without Two-Factor on the organization’s row lists only those, for owners.

On the pending invitations, Remove cancels the invitation (they can be invited again), and Change… changes the role a repository invitation offers before it is answered. GitHub cannot change an organization invitation’s role, so for one of those, Remove it and invite them again.

Account > Roles and Access also has:

Every one of these answers from what GitHub itself says, and each line names the reply it came from, such as “(GitHub: /repos/acme/web permissions)”. My Access Here reads the repository’s permissions, GitHub’s own viewerPermission, your role name (a custom role is named too), your place in the organization and its base permission, the teams that give you access, the rules on the default branch, and this sign-in’s scopes. Why Can’t They? reads the person’s real role from GitHub rather than asking you for it, then the rules GitHub says apply to the branch, and names the one that stops them.

Two things GitHub does not say, and the Workbench says so rather than guessing. GitHub’s API does not list what a role may do, so View As Role and Compare Roles show GitHub’s documented defaults for its built-in roles, say that is what they are, and then list who on this repository GitHub says has each role; a custom role is named, but what it adds is on the organization’s Repository roles page. And GitHub does not list a fine-grained token’s permissions: My Access Here says so, and when GitHub refuses something, the Workbench says the permission GitHub named in its refusal. When GitHub will not tell your account something at all (only people with write access may read others’ roles, for example), the answer says it cannot be known.

Bulk Access Changes reads each repository’s current role first, and the preview says it per person: “kelly on acme/web: write now, maintain after.” A repository where they already have that role is listed as “nothing is sent”, and nothing is.

Compare Accounts and Act As

With more than one account in Manage GitHub Accounts, Compare Accounts… asks GitHub, with each account’s own sign-in, about the open repository: its role, viewerPermission, its role name and its sign-in’s scopes, then what one may do that the other may not. Before showing anything under an account’s name, it asks GitHub whose the saved token is; if GitHub names somebody else, nothing is shown for that account, and you are told to sign in again.

Act As Another Account… does one thing as another of your accounts and then forgets it: approve the selected pull request (approving your own needs a second account), comment on the selected issue or pull request, close or reopen it, or star the repository. You choose the account, then the action. The question names the account and its server (“As kelly-test on github.com, not as you: approve pull request #7”), and so does the result (“Approved pull request #7 in acme/web as kelly-test.”). Act As is held to that account’s own Workbench level, not yours, and Safe Mode stops it like any write. It checks whose the token is first, and sends nothing if it is not that account’s. Your own account, its lists and its remembered reads are never touched: everything QUILL remembers is kept per account.

Who has what, and why

Under an organization in the tree, three lists answer “who can do what here” a row at a time, so you never have to read a grid:

Type a name, a role or a team in the filter box, or use Show Only, to narrow any of them, and Export List… (Ctrl+Shift+X), on the Workbench’s File menu, saves what is shown. When GitHub will not show part of the answer, for example a repository’s direct collaborators to someone who is not its admin, the status bar says which, rather than leaving people out silently. Set Repositories’ Custom Property… on the organization’s row gives one property a value in several repositories at once, and Issue Types under the organization lists its issue types.

Rules in plain words

A ruleset’s sheet, and a branch’s protection, list every rule as a check box with its settings, and a Summary page reads the whole thing as sentences: “On the default branch: changes need a pull request with 2 approvals including a code owner; checks build and test must pass; force pushes are blocked.” Read that page first.

A repository’s Settings > Rulesets list, and an organization’s Rulesets, show each ruleset as a sentence; Alt+Enter opens its sheet, and Delete removes it after you type its name.

An organization’s roles

GitHub gives every organization roles that reach all its repositories at once: All-repository read, triage, write, maintain and admin, the security manager, the app manager, and any custom roles. Choose Roles… on an organization’s row (in the Workbench’s Organizations place) to open Roles in that organization.

After each change QUILL reads the list back from GitHub and says what happened, such as “sam now has all_repo_write.” These need an owner’s sign-in with the admin:org scope.

An organization’s rulesets

An organization ruleset applies across its repositories. Choose Rulesets… on the organization’s row to open Rulesets in that organization. Each row gives its name, its enforcement and what it targets: “Protect main: Active, on branches”.

To make an organization ruleset from repositories that each have the same one, use Promote to Organization under Across Repositories.

Repository settings from the editor

With the Workbench in use, the editor’s Rename Repository, Change Visibility, Change Default Branch and Configure Branch Protection open the repository’s sheet at the right page, and Create Repository, Fork, Commit Multiple Files and the Codespaces commands open the Workbench on the repository and run from there.

A walk-through: labelling two issues, then taking it back

This uses the practice repository (Help > Practice on GitHub…, Ctrl+Alt+P). It changes two practice issues and puts them back.

  1. In the Workbench, go to the practice repository and press Ctrl+Shift+1 for its Issues. Press F6 until you reach the list.
  2. Press Ctrl+E, type no:label, and press Enter. The list narrows to the issues with no label. Alt+7 says the filter in words.
  3. Press F6 to come back to the list, select the first issue, then hold Shift and press Down Arrow to select the second as well. Alt+2 says how many are selected.
  4. Press Alt+Enter. One sheet opens, “Properties of 2 issues”. Ctrl+Tab moves through its pages to the one with the labels.
  5. Tab to the labels list and check “practice: question” with Space. You hear “practice: question, on”.
  6. Press Ctrl+Enter. You hear the preview, “Change 2 issues: add practice: question.”, and Enter goes ahead. The results list says Done for each. Escape closes it.
  7. Press Ctrl+Shift+H for Change History. Each issue’s change is a row of its own, newest first. Escape closes it.
  8. Back in the list, press Ctrl+Z. The label comes off the issue changed last, and you hear what was undone. Press Ctrl+Z again for the other.
  9. Press Escape in the filter box to clear the filter.

To try the same without changing anything, turn on Dry Run (Ctrl+Alt+D) before step 6: you hear what would have been sent, and nothing is.

Learn it with a guided lesson

Help > Tutorials (Ctrl+F2) has the GitHub lessons. For this chapter: