--- title: How to Test Portal Permissions and Tenant Isolation description: Test your customer portal with two companies. Check who can open each project, support request and file before inviting real customers. --- [Skip to content](https://woodsportal.digitalwoods.io/en/resources/articles/test-hubspot-portal-permissions#main-content) [![WoodsPortal](https://woodsportal.digitalwoods.io/hs-fs/hubfs/woodsportal-2026/v3234/assets/woodsportal-logo.png?width=393&height=50&name=woodsportal-logo.png)](https://woodsportal.digitalwoods.io/) [Product](https://woodsportal.digitalwoods.io/product) Use Cases [Customer Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Vendor Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Dealer Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Membership Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) [Pricing](https://staging.woodsportal.digitalwoods.io/pricing) Resources [Browse all resources](https://woodsportal.digitalwoods.io/resources) [Documentation & help](https://woodsportal.digitalwoods.io/resources/docs) [Developer resources](https://developer.dev.woodsportal.com/) [Open-source frontend](https://github.com/Digital-Woods/WoodsPortal-Frontend) [Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo) Menu [Product ↗](https://woodsportal.digitalwoods.io/product) Use Cases [Customer Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Vendor Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Dealer Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Membership Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) [Pricing ↗](https://staging.woodsportal.digitalwoods.io/pricing) Resources [Browse all resources↗](https://woodsportal.digitalwoods.io/resources) [Documentation & help↗](https://woodsportal.digitalwoods.io/resources/docs) [Developer resources↗](https://developer.dev.woodsportal.com/) [Open-source frontend↗](https://github.com/Digital-Woods/WoodsPortal-Frontend) [Get Started with WoodsPortal ↗](https://app.woodsportal.com/login/sso) [Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo) [Resources](https://woodsportal.digitalwoods.io/resources)/Articles/Check Who Can See What in Your HubSpot Customer Portal ARTICLE # Check Who Can See What in Your HubSpot Customer Portal Test your customer portal with two companies. Check who can open each project, support request and file before inviting real customers. **[WoodsPortal Editorial Team](https://woodsportal.digitalwoods.io/en/resources/author/woodsportal-editorial-team)**ArticleOctober 14, 2026 On this page Imagine two companies using the same customer portal. Northstar Foods wants to see its cooling-unit repairs. Harbor Systems wants to see its own projects. They should both find what they need. Neither should be able to open the other company's information. That is what checking portal permissions is really about. ## Meet three people who use the portal Same portal. Different people, different views. NORTHSTAR FOODS Maya · Manager Northstar projects, requests and permitted documents NORTHSTAR FOODS Ben · Team member Only the requests he is assigned HARBOR SYSTEMS Priya · Manager Harbor projects, requests and permitted documents All three use the same portal, but they should get different views. This is a fictional example for planning your own test, not a report of a completed WoodsPortal security test. ## Here's what the difference looks like Who can open what? MAYA Northstar only Own project: Yes · Own requests: Yes · Harbor project: No BEN Limited Northstar Assigned requests: Yes · Private file: Only if allowed · Harbor: No PRIYA Harbor only Harbor project: Yes · Northstar project and files: No These are example rules to configure and verify, not measured results. You make these rules in your portal setup. A person's company, their role and the specific record all matter. Simply hiding a menu item is not enough. ## Five things to check before launch Five simple checks 01 · LIST See only approved projects and requests 02 · DIRECT LINK A copied link must not reveal another customer's record 03 · FILES Downloads follow the right sharing rules 04 · ACTIONS Editing is limited to permitted tasks 05 · RELATED RECORDS Permissions still apply when following links These five checks cover the common places where a portal can look right on the screen but behave differently when someone follows a link or opens a file. ## How to test it in practice Set up two test companies and a few made-up records in a safe test environment. Sign in as Maya, Ben and Priya, one at a time. First, try the actions that should work. Then try something that should not work, such as opening another company's project using a copied URL. Record what happened. Expected outcomes — tests still need to be run SHOULD WORKMaya opens her own support request SHOULD WORKPriya opens Harbor's project SHOULD BE DENIEDPriya opens Maya's project link SHOULD BE DENIEDBen opens a private file without permission SHOULD BE DENIEDMaya edits a restricted field Those are expected outcomes, not results already measured on WoodsPortal. If a test fails, fix the relevant setup and run it again. ## What the settings actually control HubSpot holds your customer and business records. In WoodsPortal, you configure the supported information and actions each external user can access, including related records and files. **HubSpot plan note.** WoodsPortal's nested relationships between HubSpot objects use GraphQL. GraphQL is available with HubSpot Sales Hub Enterprise, Service Hub Enterprise, or Content Hub Professional or higher. Many other portal use cases can use WoodsPortal's REST API implementation on HubSpot plans including Free; supported features depend on the configuration. HubSpot also has its own support portal for customer tickets. If you use that instead, test its native ticket-sharing settings. The same principle applies: each person should see only what they are allowed to see. ## Frequently asked questions ### Is a hidden record automatically protected? No. Always try a direct link, a related-record link and a file download. A hidden list item alone is not a permissions test. ### Do I need many test accounts? Start with two unrelated companies and one team member with fewer permissions. Add more cases when your real customers have more complex roles. ### Can two people from one company see different things? Yes, where the portal roles and record permissions are configured that way. Test both accounts. ### What if someone shares a link to another customer's record? The other person should be denied unless they independently have permission. Verify that outcome with a test account. ### Are downloaded files covered by the same rules? Not necessarily. Check how each file link is shared and downloaded. A separately public file link may have different access behavior. ### Can customers change HubSpot records from the portal? Only for supported actions you enable and permit for their role. Test that unauthorized changes do not go through. ### How can I tell whether my tests passed? Write down the action, who tried it, what should happen and what actually happened. Mark each test as passed, failed or not tested. ## Start with one easy test Create two test customer accounts, give each one a different project, and try opening each other's project links. Then check files, related requests and editing rights before inviting real customers. Use the [WoodsPortal custom-role guide](https://woodsportal.digitalwoods.io/resources/docs/create-custom-portal-roles) and [Association Builder guide](https://woodsportal.digitalwoods.io/resources/docs/configure-associations-and-association-labels) for the setup steps, or explore the [customer portal example](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal). KEEP EXPLORING ## Related resources [Browse all resources ↗](https://woodsportal.digitalwoods.io/resources) ## On this page [All resources ↗](https://woodsportal.digitalwoods.io/resources) A connected experience ## Turn your HubSpot data into a customer workspace. Explore how WoodsPortal presents connected records and relevant actions to external users. [Explore the product ↗](https://woodsportal.digitalwoods.io/product)[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo) A CONVERSATION ABOUT YOUR PORTAL ## Book a meeting. Choose a convenient time to discuss your HubSpot portal. × Prefer to open the booking calendar in a new tab? [Open meeting calendar ↗](https://digitalwoods.io/meetings/woodsportal/demo) × COMING SOON ## This resource is in preparation We are preparing this resource for the WoodsPortal library. Explore other topics in the collection, or talk with our team about your portal plans. Return to resources ↗ [![WoodsPortal](https://woodsportal.digitalwoods.io/hs-fs/hubfs/woodsportal-2026/v3234/assets/woodsportal-logo.png?width=393&height=50&name=woodsportal-logo.png)](https://woodsportal.digitalwoods.io/) Your HubSpot. Their experience.A complete portal, ready to make your own. [Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo) ## Product [Overview](https://woodsportal.digitalwoods.io/product) [Pricing](https://staging.woodsportal.digitalwoods.io/pricing) ## Solutions [Customer Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Dealer Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Vendor Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Member Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) ## Resources [Blog](https://woodsportal.digitalwoods.io/en/resources) [Knowledge Base](https://woodsportal.digitalwoods.io/resources/docs) [Developer Documentation](https://developer.dev.woodsportal.com/) ## Company [DigitalWoods](https://digitalwoods.io) [Trust Center](https://trust.digitalwoods.io/) [HubSpot Marketplace](https://ecosystem.hubspot.com/marketplace/listing/woodsportal) [Privacy policy](https://digitalwoods.io/privacy-policy)[Terms of service](https://digitalwoods.io/terms-of-service)[Frontend license](https://github.com/Digital-Woods/WoodsPortal-Frontend/blob/main/LICENSE.txt) © 2026 DigitalWoods Technologies Inc.WoodsPortal is a DigitalWoods product. Northstar, Horizon and Riverside scenarios and portraits are illustrative, not customer testimonials. ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "WoodsPortal Editorial Team", "url" : "https://woodsportal.digitalwoods.io/en/resources/author/woodsportal-editorial-team" }, "dateModified" : "2026-10-16T10:36:34.904Z", "datePublished" : "2026-10-14T18:30:00.000Z", "headline" : "How to Test Portal Permissions and Tenant Isolation", "mainEntityOfPage" : { "@id" : "https://woodsportal.digitalwoods.io/en/resources/articles/test-hubspot-portal-permissions", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://woodsportal.digitalwoods.io/hubfs/digitalWoods%20logo.png" }, "name" : "DigitalWoods Technologies Inc" } } ```