Enterprise Support Portal Orientation

 Welcome to Webflow Enterprise! If you’re watching this, your organization has just taken an exciting step with Webflow — and we understand that getting started... can be overwhelming.

A new platform. New workflows. A site to build, implement, or migrate. And a team to get up to speed.

That’s not something you can do very easily all on your own. Which is exactly why it’s not just myself that will be here to guide you along the way, but the Education team is here for you as well. 

[Grimur] That’s right Miguel.

We won’t be teaching you how to build in Webflow just yet. Instead, we’ll walk you through what you can expect during onboarding, the people and resources available to help, and a few things you can focus on in your first 30 days to set your team up for success.

[Curtis] Well said Grimur.

And during onboarding, there are a few key things you’ll work through: 

Getting your Workspace, sites, and team set up,

Planning your implementation or migration of your site,

Training your team,

And preparing to launch.

[Miguel] And you won’t have to figure all of this out on your own. The entire team is here for you, along with the many resources you have available to you.

One of the first resources to know about is your Enterprise Support Portal or ESP

[Grimur] I have ESP. (Tries to move coffee cup with his mind)

[Miguel with a smile] — this is your home base, which you can find at support.webflow.com/enterprise.

From here, you can get help from the Webflow Support team, find Enterprise-specific resources, and manage common account requests.

Depending on your account and permissions, you may also see information about your Enterprise setup and usage, along with quick actions for things like requesting additional seats, enabling SSO, or making account changes.

[Curtis] Which brings up an easy first step: bookmark this page.

[Grimur with his fingers on his temples] Yes... do it. Bookmark this page.

[Curtis looking over at Grimur smiling]

[Miguel] Any time you’re not sure where to go for help, the Enterprise Support Portal is a great place to start.

Alright — let’s walk through what comes next.

First, you’ll want to get the basics in place: your Workspace, your first site, and your team.

Once you sign on with Webflow Enterprise, your Workspace is created and set up for you. If you haven’t already, log in and take some time to get familiar with it.

You’ll also want to configure important Workspace settings for your organization, such as SSO or two-factor authentication.

Next, you'll set up your site — whether that means building something new or transferring an existing one into your Enterprise Workspace. More detailed instructions live in the Help Center whenever you need them.

From there, it’s time to bring in your team.

Invite the people who will be working in Webflow, then assign roles and permissions based on what each person needs to do.

We have an entire Webflow University course dedicated to this — it walks through how to structure access so the right people can do their jobs without giving everyone more permissions than they need.

[Grimur] I just deleted everything!

[Curtis] We didn’t give you access yet.

[Grimur] Well I just deleted something.

[Miguel] Which is exactly my point. Taking the time to get this right early gives your team a much stronger foundation for the work ahead.

Once the foundation is in place, the next step is planning how your site will come together.

Your implementation may look very different depending on whether you’re building something new, migrating an existing site, or moving an existing Webflow site into an Enterprise Workspace.

Whatever your path, the Enterprise Support Portal has you covered with Pathfinder

[Miguel] Eh? Get it? Path... Pathfinder

[Curtis] That wasn’t bad.

[Grimur] It was okay.

[Miguel] Pathfinder is an AI-powered Solutions Architect designed specifically for Enterprise customers.

This is a resource worth using early in your onboarding.

Rather than giving you generic recommendations, Pathfinder can use information about your Workspace and project to provide guidance tailored to your implementation.

For example, it can help you think through:

how to structure a design system,

how different roles might participate in your implementation,

what your project timeline could look like,

and what to review before launch.

[Curtis] That will definitely get you on the right PATH.

[Grimur laughs loudly] Haha! Good one! So funny.

[Miguel irritated] What? That’s what I just—I made that joke first!

[Grimur] No. No. Curtis’ was way better.

[Curtis winks at Miguel]

[Miguel] Anyways, It can also point you toward relevant Webflow University resources along the way.

A great time to use Pathfinder is near the beginning of your onboarding process, while you’re still deciding how you want to approach your implementation or migration. To start, you’ll provide context and answer questions in order to receive personalized recommendations and guidance for your specific project. 

Of course, a successful implementation isn’t just about how your site is built. Your team also needs to know how to work in Webflow.

And not everyone needs to learn the same things — A designer, marketer, content editor, reviewer, and Workspace admin may all use Webflow very differently.

That’s why Webflow University organizes learning around what people are actually trying to do. You’ll find role-based learning paths for the core site roles — Designer, Marketer, Content editor, and Reviewer.

Each learning path starts with a short orientation to Webflow itself — where your work actually happens, how to navigate the platform, and how your role fits into the team’s workflow.

From there, team members can continue into the learning that’s most relevant to what they’ll actually be doing.

The main thing to remember here is don’t leave training until the week before launch.

[Grimur looking at Curtis with disapproving nods]

[Curtis looking confused]

As you’re planning the implementation, plan for learning too. Giving people time to get comfortable with Webflow early makes the rest of the process much smoother.

Different questions call for different resources.

• Webflow University is where you go to learn how to use Webflow and build your skills.
• The Help Center is where you go for product documentation, troubleshooting, and answers to common questions.
• Webflow Way is where you go for guidance on Webflow best practices and recommended approaches.
• Developer documentation is where you go for technical guidance on APIs, integrations, and developer workflows.
• Pathfinder is where you go for personalized guidance on your implementation or migration.

When you need additional help, Webflow Support can help with technical issues, implementation questions, and other challenges that come up along the way.

Depending on your Enterprise plan, you may also have access to a Customer Success Manager or Solutions Architect for additional guidance.

On-screen CTA: Check your Account Team details in the Enterprise Support Portal to learn more.

6. Preparing for launch

As your implementation comes together, the next milestone is your first full-site publish.

This is where all the pieces you’ve been working on — your site structure, content, design system, team workflows, domains, and technical setup — need to come together.

And this is one area where you don’t want to rely on memory alone.

Webflow University has a dedicated course called Prepare to publish your site, which walks you through the major steps to review before publishing.

You’ll also have access to a pre-launch checklist you can use to make sure important details don’t get missed.

That includes reviewing things like your content and links, responsive layouts, SEO settings, forms, redirects, domains, analytics, and other launch-critical configuration.

[Grimur] Don’t forget Optimize

[Miguel] Yes. And optimize. Depending on... 

[Curtis] Localize.

[Grimur] Yeah! Localize. That’s another one.

[Miguel] Yes. Thank you guys, I was just naming a few to get the point across. But... 

Depending on your implementation, there may also be organization-specific checks your team needs to complete.

So give yourself time to work through the checklist well before your planned launch date.

[Grimur] What about MCP 2.1. That’s great! That’s a great one.

[Miguel amused] And if something comes up along the way, use the resources we’ve already covered — Pathfinder, the Help Center, Webflow Support, and your Webflow team — to work through it.

Think of launch as a series of confidence-building checks that help your team make steady progress toward publishing. Each one brings you closer to a launch you can feel confident in.

7. What support looks like after launch

After launch you can keep using the same self-service resources you used during onboarding including Webflow University, the Help Center, etc.

And once your site is live, you can also book a Health Check through the Enterprise Support Portal. These are free, 30-minute, one-on-one sessions with a Webflow Support team member focused on areas like design systems, content management, or governance. 

Webflow Support is also still here to help after launch, whether you’re troubleshooting an issue or working through a question about how to best use Webflow. 

And if your agreement includes a Customer Success Manager or Solutions Architect, they can continue supporting your team through things like success planning, technical workshops, and helping your team build deeper expertise with Webflow as your needs grow beyond your initial use case.

8. Your first 30 days

‍

[Curtis] And so, with all of those resources available, what should you actually focus on first?

Here’s a simple framework for your first 30 days with Webflow Enterprise:

1. Bookmark your Enterprise Support Portal: I can’t stress this enough — This is your home base for Enterprise-specific resources, account requests, and help. Bookmark it. Now.
2. Set up your Workspace, site, and team: Configure your Workspace, set up your site, invite the right people, and give them roles and permissions that match how they’ll be working in Webflow.
3. Run Pathfinder to plan your site build, implementation, or migration: Give Pathfinder context about your implementation and use its personalized guidance to help shape your build, implementation, or migration plan.
4. Train your team: Have team members start the Webflow University learning path that best matches their role so they can learn the parts of Webflow they’ll actually use.
5. Start preparing for launch: Use the Prepare to publish your site course, the pre-launch checklist, Pathfinder, documentation, Support, and your Webflow team to work through the final details.

[Grimur] In fact, you don’t have to do everything at once. In fact — again — we don’t recommend it. But if you make progress on these five things in your first month, you’ll have a strong foundation for everything that comes next.

9. Closing

[Miguel] Webflow Enterprise gives you more than a platform to build on. You also have an ecosystem of resources to help your team learn, solve problems, and keep improving. So just to recap

• Use Webflow University when you want to learn.
• Use the Help Center when you need documentation or an answer to a product question.
• Use Pathfinder when you want personalized implementation guidance.
• And use the Enterprise Support Portal and Webflow Support when you need help from us.

There’s a lot that goes into adopting a new platform, and you don’t need to learn or solve everything on day one.

You have resources to guide you through each stage — from your first login, through implementation and launch, and well beyond.

Welcome to Webflow. We can’t wait to see what you build.

‍