Help

New: Portals Beta

cancel
Showing results for 
Search instead for 
Did you mean: 
Ayesha_Bose
Airtable Employee
Airtable Employee

Hello! I’m Ayesha, a Product Manager here at Airtable. We’re so excited to announce that we now have Portals available in Beta for customers to unlock guest access for their organization.

Portals - Image 1.png

 

What are Portals and why would you use them?

With Portals, you’ll be able to invite users outside of your organization as guest users to your interfaces. These guest users will see a custom sign-in screen and be able to collaborate inside your interfaces together.

We recommend using Portals for key use cases like:

  • Client portals
    • Ex: A marketing agency giving their clients real-time access to project updates and deliverables
  • Vendor management
    • Ex: A plumbing supply distributor who works with major appliance brands and needs to centralize vendor info
  • Customer support
    • Ex: A digital product organization who is giving customers a way to see their roadmap and provide suggestions

 

How do you get access to the beta?

If you’re on a Team, Business, or Enterprise Scale account, please visit airtable.com/account for instructions on how to get access.

 

How do you enable Portals and invite guest users?

Any interfaces can be shared as a Portal (so you don’t need to build a new app if you already have one you’d like to share with your external collaborators).

Once you’re in the beta, you’ll be able to see a new tab inside the Share dialog on interfaces:

Portals - Image 2.png

 

After you enable a portal, you’ll be able to select specific interface sections and share with guest users as Editor, Commentor, or Read-only access — just like regular Interface collaborators today.

 

What does the experience look like for a guest user?

Today, they’ll see a simplified version of the Airtable sign-in screen and be able to create a new account or login. Inside the app, they’ll be able to do everything a regular interface collaborator can do with a couple of key exceptions:

  • They will not be able to share the app with anyone else
  • They will not be able to navigate to the data layer or go back to the Airtable home to see other bases in your organization.

Other common questions:

  • How do permissions work on Portals?
    • Permissions behave the same way as they do on Interfaces in general (which you can read about in our support article).
    • With Portals, we recommend two specific Permissions-related features to have the best experience:
      • Make sure that someone only sees the data that’s for them: use our filter on the email address or collaborator fields to filter data to just the information that’s tied to the current user.
      • Hide external user information: in your interface page settings, turn on the sharing restriction setting to prevent external users from seeing each other.
  • What restrictions do guest users have?
    • These users will have to be outside of your organization.
    • They can only be added to interfaces that belong to 1 base. If you add them to the underlying data or any other apps, they will be billed as a regular collaborator.
  • How does pricing work?
    • The Portals add-on is available for Team plan customers starting at $120 per month for 15 guests and 1 portal. For Business and Enterprise customers, custom pricing is available. Bulk discounts are available for large volumes of guests.
    • Billable seats for guest users will be counted when a guest user is invited to your portal app with editor or commenter permissions on the Team plan.
    • Additionally, guest users will be charged as a full collaborator seat if they are added to multiple apps in your organization or if they are invited to the underlying base for your app.

We’re looking forward to hearing what you think, so please let us know if you have any questions!

19 Comments
Databaser
12 - Earth
12 - Earth

The pricing model is a joke. That's no way to price a "portal". Once again, it's all being developed with big enterprises in mind 💰💰 It's their good right, but I long for the days when they wanted to "democratize software creation by enabling anyone to build the tools that meet their needs"...

Ayesha_Bose
Airtable Employee
Airtable Employee

Hi all!

Sorry for the delay in getting back to you, it's been a busy and exciting week since we've launched this beta publicly! If you want to follow up on anything specific, please don't hesitate to email me at ayesha.bose@airtable.com.

Overall, thank you for your feedback on pricing. This is something that we're actively thinking about (especially as we continue to build out more features for Portals like custom branding), so really appreciate the signal here. While we're in beta, we're still looking to get feedback on a lot of the experience, including pricing, and we'll share more updates on this as we have them.

---

  • @kuovonne :

    • If a company needs fewer than 15 portal users, is the price still $120/month?

      • Yes — you'll be able to purchase buckets of portal guest users and that's our smallest bucket now.
    • You state “Billable seats for guest users will be counted when a guest user is invited to your portal app “. Does a portal user become billable upon being invited to the portal, or upon accepting the invitation and accessing the portal? For example, if someone is invited but never actually accepts the invitation, are they billable?

      • They will not be billed until they sign into the portal (which is accepting the invite).
    • If portal users are added and removed throughout the month, such that over 15 people access the portal throughout the month, but there are only 15 “active” people at a time, will owners be charged for only 15 portal users?

      • Yes, as long as they are removed from the portal, they will only be charged for 15 guest users.
    • Is it possible to add/remove/activate/deactivate/change permissions via the web API or similar?

      • No, we don't support this, but I could see how this could be helpful for many use cases! I'll share with the team.

  • @ScottWorld:
    • Single-record page: thanks for flagging this and sharing details on how this would be helpful! This is on our backlog and we've talked about this a bit, but will share your feedback with the team.
ScottWorld
18 - Pluto
18 - Pluto

Thanks so much, @Ayesha_Bose! 🙂

Great to hear that single-record pages are on your backlog! 🙂

Also, has Airtable considered "simultaneous user pricing" like I outlined above? That could make portals extremely affordable for your users.

Thanks!

- ScottWorld, Expert Airtable Consultant

Tristan-ARG
6 - Interface Innovator
6 - Interface Innovator

Yes! I want to pay for this feature, but give me some reasonable price ladder 😂

kuovonne
18 - Pluto
18 - Pluto

@Ayesha_Bose Thank you for the clarifications. 

Some more feedback …

Limiting portal pricing to one portal per person seems like it could cause issues. When different people are in charge of different bases within a company, it can be hard to know who has access to other bases. If two different staff members invite the same external user to their respective portals, it sounds like that external user will cost the same as a full internal user versus the lower portal seat price. However, neither staff member is aware that the external user has access to multiple portals to explain the higher rate. 

I also prefer the idea of pricing based on concurrent portal users, versus named portal users.

Another pricing idea is to charge per edit operation instead of by portal user. For example, a portal could have a monthly bucket of 500 (or 5,000 or 50,000) edit operations. This could be 500 portal users each updating their own record one time. It could be 5 portal users each updating twenty records once a week, with a few operations left over. This would be similar to how automations currently have run limits. (But if you go with this option, please enable users to easily or automatically purchase additional buckets of edit operations mid-month!) I know that there would be a lot of engineering required to support this pricing model, but it seems like a fairer way to balance out the cost of lots of portal users who might need to perform very few edits.

ScottWorld
18 - Pluto
18 - Pluto

@kuovonne 

Ooh, that’s a clever idea of charging per edit!

Either that or concurrent users would be ideal.

@Ayesha_Bose As Kuovonne mentioned above, if you charged by the edit, we would need a way to purchase more edits, because this is currently one of the biggest obstacles in Airtable: There is currently no way to have more than 50 automations in a single base, and there is no way to purchase more automation runs. This is one of the big reasons that people turn to Make’s Airtable automations.

Thank you!

- ScottWorld, Expert Airtable Consultant 

Tristan-ARG
6 - Interface Innovator
6 - Interface Innovator

yes!, pay per edits sounds good and fair!!

Cody_Winchester
6 - Interface Innovator
6 - Interface Innovator

I apologize in advance for turning this into a rant within this thread but I'm frustrated with this latest offering:

Our company has been using Airtable for over 5-years now and we love it. However, we have seen a noticeable turn away from what made the product so accessible and powerful which is further evidenced by this latest beta with Portals.

First, we noticed less accessibility to support. Direct messaging turned to bots that delivered dead-ends, and then a ticketing system that was long in response times. When support was reached, the folks were really helpful, but enough time had passed that problems became moot as workarounds had to be employed. The support community, though is absolutely top-notch! Kudos to the experts that are active here!

Then we saw the pricing structure change (we're still on a legacy Teams plan). We investigated the Enterprise tier to access more security and administrative features, but were left with an astounding 3x price increase per user given the extent of added features. The scale of our group just can't expand enough to gain any benefit from marginally more helpful features.

Next came the AI features as an extra cost per user per month. We had used it in beta and saw some promise, but without being able to compartmentalize users and bases the added cost per user to leverage these features was just nonsense.

Finally, we have this new product, Portals, going into beta. Again, there's a pricing model that totally breaks the camel's back. While I'm sure that the product will be beautiful and accessible for average users to build, the problem again becomes an issue of scalability. Airtable, you all really need to look at how to break this micro-transaction model that bloats costs versus the benefits of the products. This just doesn't feel like it's in the start-up spirit that made Airtable so great in the past.

When the costs of all these features come to bear they simply outweigh the benefit. When a company is paying north of $50k / year for Airtable tools, it begs the question if there are more formal database solutions that should be sought instead.

I implore Airtable to rethink the strategy of these past couple of years and look toward bundling all of these features into neat and economical packages that are more powerful and palatable to more customers. Until then, our group will stay in our lane and pass on Portals or whatever else comes to avoid these costly additions. 

Peter_Nelson2
6 - Interface Innovator
6 - Interface Innovator

Is there a way to selectively enable/disable interfaces within a section? I have several interfaces defined that only internal administrators should be accessing and for shared public access I want to be able to choose only specific interfaces with limited access based on user permissions. I'm not seeing an easy way to manage that in the Portals beta. When I share an interface, a portal guest seems to get access to all interfaces within a section by default.

Ideally I'd like to be able to manage external (portal) users by selecting exactly which interface elements within any given base interface section they should have access to.