New Permissions Layer for Notion Solves Contractor Access Issues

A developer has created a solution to the high costs associated with providing contractor access to Notion databases. The problem stems from Notion's native sharing features, which are either read-only or require expensive full seats for users who only need access to specific data. The new tool acts as a permissions layer, allowing contractors to view and edit specific rows and columns without a full seat.

The technical implementation relies on Notion's OAuth API and a backend built with Supabase and PostgreSQL. This setup allows for real-time data synchronization and strict role definitions. The pricing model is a flat $59 per month for unlimited users, offering significant savings compared to paying per-seat fees. While currently in beta, the tool aims to expand its feature set based on user feedback.

Managing contractor access to internal data presents a significant challenge for many agencies using Notion. The core issue is the inability to provide granular permissions that allow for both viewing and editing specific data points. Agencies often need to share CRM or project tracker data with external workers while keeping sensitive information like pricing, margins, or other clients' data hidden.

Notion's native features fail to address this specific need adequately. The platform offers row-level filtering, but it is strictly view-only, preventing contractors from making necessary updates. Additionally, column hiding is not a native feature, and guest sharing is restricted to read-only access. Consequently, agencies are forced into two inefficient options: paying $15 per month for full seats for every contractor or duplicating databases, which creates a maintenance nightmare.

The financial impact of these limitations can be substantial. Based on the cost structure of full seats, the expenses scale quickly with the number of contractors:

• 5 contractors cost $900/year in wasted seat fees.
• 20 contractors cost $3,600/year.
• 50 contractors cost $9,000/year.

These costs prompted the development of an alternative solution that bypasses the per-seat model entirely.

The developed solution is a permissions layer that integrates directly with Notion using its OAuth API. This integration allows the tool to act as an intermediary, controlling exactly what data contractors can see and edit. The system is designed to be a clean portal where contractors can interact with data without needing direct access to the internal Notion workspace.

Functionally, the tool allows administrators to define specific roles. For example, a role can be set so that sales representatives only see leads where they are the owner, while simultaneously hiding the pricing column. Contractors access this data through a dedicated portal where they can view and edit information in real-time. The system syncs with Notion every 5 minutes to ensure data consistency.

Under the hood, the architecture consists of:

• Frontend: Built using React and TypeScript.
• Backend: Utilizes Supabase with a PostgreSQL database, employing Row Level Security (RLS) to manage data access strictly.
• Authentication: Handled via Notion OAuth 2.0.

This technical stack ensures that data remains secure and that permissions are enforced at the database level, preventing unauthorized access.

The pricing model for this permissions layer is designed to be cost-effective for teams of any size. Instead of a per-seat charge, the service is offered at a flat rate of $59 per month for unlimited users. This pricing structure directly addresses the financial inefficiency of paying for full Notion seats for contractors who only need partial access.

Currently, the project is in its beta phase and has onboarded 50 beta testers. The creators are offering an introductory price for early adopters. The first 20 customers will have their subscription locked in at $49 per month. After the initial launch period in January, the price is set to increase to $79 per month for new subscribers.

While the tool solves a critical workflow issue, it currently has several limitations that are noted on the development roadmap:

• It supports Notion databases only and does not work with pages.
• Data synchronization is not instant, occurring every 5 minutes.
• Users must manually define roles; there are no pre-set configurations.
• Team permissions are not yet available but are planned for future releases.

A free trial is available for interested parties to test the functionality.

The development team is actively seeking feedback from users to refine the tool and expand its capabilities. They are specifically looking for insights into additional permission use cases that may not currently be covered by the existing feature set. Understanding diverse organizational needs is a priority for the roadmap.

Additionally, the team is gauging price sensitivity within the market. By understanding what potential customers are willing to pay, they aim to strike a balance between providing value and maintaining a sustainable business model. The goal is to build a robust tool that solves the complex problem of external data access within the Notion ecosystem.