Write, propose and review wiki pages; recover from storage errors.
Reviewed · 2026-10-12
On this page · 6
1. Open the wiki and choose a structure
- Open a grant or one of its projects, then Grant wiki → Open wiki. All child projects use the same grant wiki.
- The wiki does not automatically copy every source. Create topics people repeatedly need: research overview, methods, data and analysis, results and decisions.
- Create an overview first. Expand Placement and edit reason and select Use as wiki start page. Keep it at the top level. Pin other important pages.
- Current wiki editors in Editor settings lists names, usernames and access roles. Editors use Create page to write and publish directly. Other participants use Propose a new page to submit a title, content, sources and reason. Pending proposals are visible only to their author and reviewers. Approval publishes a new top-level page; rejection creates no page.
2. Write a page and curate key sources
- Choose Create page and enter a title and short description. Select a parent to nest the page, for example preprocessing and evaluation under Methods.
- Write Markdown, using the heading, bold and table tools. Check Preview. Headings from # to #### produce a table of contents automatically.
- Mention researchers with @username and search accessible documents with [[. For a bibliography entry, link the paper title to its actual DOI address and add the author, year and explanation. Use the editor link tool and check Preview.
- Under Collect key sources, search by title and select a result. Explain its importance in the body. You can also use [[ directly, with one citation per line. Limits are 30 key sources and 12 inline citations.
- Source cards keep links rather than copying entire documents. Inaccessible sources show an availability message without revealing their titles. Manually pasted prose is not automatically redacted: do not paste private research originals.
3. Images and publication
- In a new page, Edit page or an edit proposal, place the cursor in the body and choose Add image. A JPG, PNG or WebP is inserted at that position; saving a draft first is no longer required. Files must be no larger than 1.5 MB and 16 megapixels; stored images are resized to at most 1600 pixels per dimension. SVG and automatic remote images are unsupported.
- A page permits up to 20 new files and images in its body. Upload starts are limited to 50 per user per day and three unfinished uploads at a time. Images require page permission; ordinary readers can access only images in the current body.
- Publish shares with currently authorized grant and child-project participants. Only current editors see drafts. Saving a published page as a draft hides it from ordinary readers.
- Bookmark published pages and discuss them below. Body @mentions link researchers; saving the body does not send alerts. Use discussion comments and mentions when notifications are needed.
4. Find, collaborate, restore and export
- Search titles or descriptions. Lists show 18 pages at a time; child-page links navigate the hierarchy. The start page and recently organized pages appear on the right.
- Grant and lab managers can edit directly and review proposals by default. In Editor settings, search by name or @username under Additional reviewers and editors, select people and save. Remove a selected chip with × and save to revoke additional access. Participants can still propose edits. Additional editors cannot grant access to others. Losing grant access also revokes wiki access.
- In Revision history, select a version to view its body and compare against the current page. Restore as a new draft preserves history and creates a new revision. Review and republish it. Renaming a page preserves its URL.
- Concurrent edits show a conflict rather than overwriting a saved change. Keep your input separately and merge it with the latest version.
- Trash preserves content and history. Move or trash child pages first. Open the Trash tab and Recover as draft.
- Use the top share icon to share to a channel or copy a link, and the star to add or remove a favorite. Recipients still need permission to read the page. The export icon offers print view, PDF, Markdown, text, and Markdown and images ZIP. ZIP includes the current page and used images. Only currently accessible citations are exported; relative platform links refer to the original site. Wiki bodies, images, revisions and proposals are stored in the lab’s preconfigured Google Drive. The server retains permissions, hierarchy, Drive references, titles and descriptions. Open Editor settings → Wiki storage in Google Drive to check pending migration counts. Existing content leaves the live DB only after upload and download verification. Keep your input and retry when a storage error appears; a failed save is never reported as successful. Edit through the platform: changing or deleting Drive files directly fails integrity checks. After server loss, restore the operational DB and separately held recovery keys first, then use the Drive wiki index. Drive content alone does not restore authentication or permissions.
- All grant and child-project participants can select Propose an edit on a published page. Enter the proposed title, content, sources and reason, then submit. The original remains unchanged. Edit proposals lists your own proposals, or all grant proposals for reviewers. Reviewers compare the changes, preview content, add a review note and approve or reject. If the original changed in the meantime, submit a new proposal based on its latest version. Approval adds a new revision.
Insert files and images inside the body
- Open a new wiki page, Edit page, a new/edit proposal, Write report, or a manual magazine article.
- Select the Notion connection for a report or the lab for an article first. That lab needs a configured private Google Drive archive.
- Click the insertion point inside the body. Choose Attach file for PDF, DOCX, HWP, TXT, Markdown, ZIP and other supported files, or Add image for PNG, JPEG or WebP.
- Limits are 20MB per file, 1.5MB per image and 20 attachments per document. Once Drive storage is confirmed, a download link or image Markdown appears at the chosen position. Images are normalized to safe JPEGs.
- Check Preview, then save/publish or submit the proposal. Use Retry attachment or Cancel attachment if transfer fails. If Google archive authorization has expired, keep the editor open, use Open archive account settings in a new tab, reconnect the existing account and retry. No new folder is needed. Ask your lab administrator to reconnect if you cannot manage settings. Finish uploads before saving.
- Before saving, only the uploader can access new files. Pending proposal files are available only to the author and reviewers. Saved files follow the document audience, including Only me and revoked memberships.
- Notion exports and wiki ZIPs retain authenticated platform links for new attachments. They do not make files public or copy large originals into the ZIP. Download originals using their links. Read-only collected documents are still edited in their original service.
Reconnect an unavailable wiki store
1. If the list opens but the body says Wiki storage is unavailable, keep any unsaved text separately. The error alone does not mean the document was deleted.
2. Open Lab management → AI/Drive preservation → Connect Google Drive archive account. Sign in and consent with the account holding the existing wiki. This is separate from project Drive reading and personal file-picker authorization.
3. Do not create a new archive folder or change its address just to reconnect. Reopen the original page and check its body and revision history.
4. If it still fails, ask the administrator to check folder access with that account, preservation enablement, storage and revoked Google access. Do not overwrite an uncertain result with a blank page.
5. OAuth apps in Testing can have authorization expire after seven days. For recurring failures, ask the administrator to check publishing status and Google policy. Never include passwords or tokens in a ticket.
6. If consent returns “Another lab operation is in progress,” your existing connection was kept and the new authorization was not saved. Wait briefly, then start a new Google account connection from the same AI/Drive preservation settings. Do not refresh the failed callback or reuse its authorization URL. You do not need to stop ongoing research work.
Official guidance: https://developers.google.com/identity/protocols/oauth2#expiration