For guilds, the Notion Admin is a paid role via the Automatic Member-Based Guild Funding model. Each guild receives 1000 BANK per week in funding for this role to help support a decentralized approach to Notion administration. It is up to each guild to determine how to use these funds and up to each guild’s Notion Admin to ensure that their own space is being managed appropriately.
Responsibilities covered under the scope of this program are outlined on the Group Notion Admins page and are limited to basic admin tasks.
Other Notion work (page updates, content creation, etc.) may be compensated however the group sees fit, but guilds are funded seasonally to ensure the core administrative functions are being covered for site security and DAO members have a clear contact person when questions arise.
For departments or projects, a primary contact or Notion page champion is recommended. Departments may choose to include these responsibilities in an existing role or create a micro-role, but there should always be someone who owns the basic Notion user and permission management for a group. Core responsibilities are as follows:
Permissions management for projects will, by default, fall under the responsibility of the Notion Administration Team unless the project teams choose to keep their permissions management in-house and identify a primary contact for Notion needs.
Join the weekly meetings on Mondays at 9pm UTC in the Coworking Yurt channel or check the weekly meeting notes async to learn of action items for the week. Attendance at the weekly meetings is not required. Participation beyond maintaining the basic security requirements is voluntary, but encouraged if you would like to get involved.
If you have committed to any open action items on the workstream’s Kanban board and prefer to work async, be sure to follow up with updates on any of your open Kanban cards for the rest of the team before the next weekly meeting.
Feel free to reach out to the Notion Admin team for any assistance. We would be happy to assist with user permissions or content clean-up, if needed.
Especially in collaborative workspaces, it can be unclear how to organize and cull files from the shared workspace. As a primary objective, keep the space clean and up-to-date. It should be easy for page visitors to find what they’re looking for and pages should appear professional to all.
As such, the site should be as searchable as possible, too. Having duplicate files or outdated information clutters and bloats the site-wide search results.