app-sharing
Manage Glide app access, privacy, authentication, and publishing.Use when configuring who can access an app, setting up sign-in methods,publishing apps, inviting users, or configuring Row Owners for data security.
When & Why to Use This Skill
This Claude skill provides comprehensive management for Glide app deployment and security. It streamlines the configuration of privacy settings, user authentication methods (including SSO and Google OAuth), and data-level security through Row Owners. By automating the publishing and invitation workflows, it ensures that business applications are correctly shared with the right audience while maintaining strict data privacy standards.
Use Cases
- Case 1: Setting up private internal tools for employees using domain-based access (e.g., @company.com) and Google authentication.
- Case 2: Configuring secure customer portals where Row Owners ensure users can only access their specific data records.
- Case 3: Managing the end-to-end publishing process for public directories, including custom URL setup and branding.
- Case 4: Implementing multi-factor authentication and access request workflows for sensitive business applications.
| name | app-sharing |
|---|---|
| description | | |
Glide App Sharing
Accessing Access Settings
- Go to Settings tab (top navigation)
- Click Access in the settings menu
- URL:
go.glideapps.com/app/{appId}/settings/privacy
Privacy Modes
Private App
- Only users you choose can access
- Users must be in the Users table or meet specific criteria
- Best for: Internal tools, member-only apps
Public App
- Anyone with link can access
- No sign-in required (optional sign-in available)
- Best for: Public directories, info apps
User Access Options
When app is Private, choose who can sign in:
| Option | Description |
|---|---|
| Users table | Only users in the Users table can sign in |
| Team members | Members of your Glide team can sign in |
| Allowed email domains | Users with specific email domains (e.g., @company.com) |
| All emails in table | Any email found in a specified table column |
Users Table Access
- Select which table serves as the Users table
- Users with emails in that table can sign in
- Common for: Employee apps, member portals
Team Access
- All members of your Glide team can sign in
- No need to add them to a table
- Common for: Internal team tools
Domain-Based Access
- Allow anyone with email from specific domains
- Example: Allow all @acme.com emails
- Common for: Company-wide apps
Authentication Methods
Configure how users prove their identity:
| Method | Description | Setup |
|---|---|---|
| Pin emails from Glide | Glide sends PIN code via email | Default, no setup |
| Magic link | One-click sign-in link in email | Enable checkbox |
| Sign in with Google | OAuth via Google account | Automatic |
| Single sign-on (SSO) | Enterprise SSO integration | Enterprise plan |
| Pin texts from Twilio | SMS PIN codes | Connect Twilio |
| Pin emails from Gmail | Send from your Gmail | Connect Gmail |
| Pin emails from Microsoft | Send from Microsoft account | Connect Microsoft |
Magic Link Option
Under "Pin emails from Glide", enable:
- Include magic link to sign in without PIN
- Users can click link instead of entering PIN
Access Requests
Allow new users to request access:
- Enable "Allow visitors to request access"
- New users see "Request Access" on sign-in screen
- Team reviewers approve/deny requests
- Manage reviewers in Team Members settings
Publishing Your App
Publish Button
- Click Publish (top right, green button)
- Makes app available at its URL
App URL
- Format:
{app-name}.glideapp.io - Custom domains available on paid plans
Before Publishing Checklist
- Set appropriate privacy mode
- Configure authentication
- Test as different user types
- Review data access (Row Owners)
- Set up branding (name, icon)
Inviting Users
Method 1: Add to Users Table
- Go to Data Editor
- Open Users table
- Add rows with user emails
- Share app URL with users
Method 2: Share Link
- Publish the app
- Copy app URL
- Share with users
- They sign in with configured auth method
Method 3: Team Invitation
- Enable "Team members" access
- Invite users to your Glide team
- They automatically get app access
Row Owners (Data Security)
Critical: Access settings control who can enter the app. Row Owners control what data they see.
Setting Up Row Owners
- Add email column to your table
- Make it a Row Owner column
- Users only see rows where their email matches
Important Notes
- Visibility conditions are NOT security (data still downloads)
- Row Owners provide true data-level security
- Use for sensitive data protection
Testing Access
Test as Different Users
- Use "Viewing as" dropdown (top of preview)
- Select different users from Users table
- Verify they see correct data/screens
Test Sign-In Flow
- Open app in incognito/private window
- Go through sign-in as new user
- Verify authentication works
Common Access Patterns
Employee Directory (Private)
Privacy: Private
Users: Team members OR Users table
Auth: Sign in with Google + Pin emails
Row Owners: None (all employees see all)
Customer Portal (Private)
Privacy: Private
Users: Users table (customers)
Auth: Pin emails from Glide + Magic link
Row Owners: Customer email column
Public Information App
Privacy: Public
Users: Optional sign-in
Auth: N/A or Sign in with Google
Row Owners: None
Internal Tool (Restricted)
Privacy: Private
Users: Allowed email domains (@company.com)
Auth: SSO or Google
Row Owners: Department-based
After Building: User Invitation Flow
After building an app, ask the user:
- "Who should have access to this app?"
- "Should it be private or public?"
- "Do you want to invite specific users now?"
Then:
- Configure privacy settings
- Add users to Users table if needed
- Set up appropriate authentication
- Publish the app
- Share the app URL
Troubleshooting
Users Can't Sign In
- Check they're in Users table (if using)
- Verify email matches exactly
- Check authentication method is enabled
Users See Wrong Data
- Review Row Owner settings
- Check visibility conditions
- Test as that specific user
Access Request Not Working
- Ensure feature is enabled
- Check team has reviewers assigned
- Verify email deliverability