Frequently asked questions

No. WoodsPortal is built directly on HubSpot and does not store CRM data in any external database. All data remains inside your HubSpot account and follows your existing permissions and security rules.

Yes. Customers can securely access custom objects and related records such as projects, assets, onboarding tasks, or contracts based on the associations and permissions you define in HubSpot.

WoodsPortal supports multi-user, multi-entity customer accounts. You can expose data across parent companies, subsidiaries, locations, or projects while controlling visibility using HubSpot associations and role-based access.

Yes. You can assign role-based access so each customer user sees only the data relevant to them, such as finance users accessing invoices while operational users access projects or tickets.

WoodsPortal inherits HubSpot’s security model, including authentication, permissions, and auditability. Since data never leaves HubSpot, compliance and governance are easier to maintain without introducing new systems.

Yes. WoodsPortal can replace external portals, spreadsheets, or shadow CRMs by exposing HubSpot data directly to customers in a controlled and secure way.

You control which objects, records, and actions are available to customers. The portal can be branded and configured to match your workflows without custom development.

Absolutely. WoodsPortal scales from simple ticket and document portals to complex enterprise customer experiences, making it suitable for growing teams and mature organizations alike.

Most teams can connect WoodsPortal and launch a basic portal quickly using their existing HubSpot data. More advanced setups can be rolled out incrementally without disrupting current operations.