Overview
NextGen organizes work in workzones (team or departmental spaces) and frames (structured tables of items with columns such as title, status, assignee, and dates). Teams switch between list and Kanban views, apply filters, and collaborate in real time where the product supports it.
The steps below assume you are setting up a new team environment. If you join an existing organization, some stages may already be complete; skip to the sections that match your role.
Prerequisites
- A supported, up-to-date web browser on desktop or tablet (Chrome, Edge, Firefox, or Safari).
- A valid business email for account creation, unless your organization uses a different approved identity flow.
- Clarity on who will own billing and who will administer users—often different people in mid-size and larger companies.
Account and onboarding
Registration collects essential context: organization or team name, intended use case, and initial workspace configuration. Completing these steps ensures your default navigation and sample structure align with how you plan to work.
During onboarding, note which workzone becomes your primary space. You can add more later, but the first one often becomes the anchor for early frames and members.
If your company uses invitations, accept the invite before creating a parallel organization to avoid duplicate tenants and split visibility.
Workzones and frames
A workzone is the boundary for a set of frames and members. It helps separate departments, clients, or programs without mixing permissions across unrelated work.
A Frame holds groups of items, each with column values driven by your column definitions—text, status, people, dates, tags, files, and more, depending on configuration.
Before inviting a large group, confirm column definitions match how your team tracks work. Renaming or restructuring columns later is possible but easier early in the rollout.
Your first frame session
- Open the dashboard and select the correct workzone. Verify you see the frames you expect; if not, check with your administrator for access.
- Open a frame from the navigation or home. List view is a common default for scanning and editing many fields at once.
- Create or select an item. Fill title and key fields first; optional fields can follow once the item exists.
- Validate permissions by confirming you can edit cells your role should control. If something is read-only, your frame role may be view-only or limited to specific columns.
- Switch layouts using the frame’s view controls—try Kanban to validate status columns and drag-and-drop rules, if enabled for your role.
- Apply a filter or search to simulate day-two usage when the frame grows. This surfaces whether naming conventions and statuses are sufficient.
- Invite a colleague with the minimum role required for their job (for example, collaborator versus editor), then confirm they see the same frame and item updates.
List, Kanban, and personal views
List view suits operational reviews, bulk edits, and spreadsheet-style scanning. Sorting and column filters help large teams stay focused.
Kanban view maps items to status-driven columns. It is ideal for pipeline and stage tracking when your status model is stable and agreed upon.
Personal views (where available) let individuals filter the same underlying frame to their assignments or priorities without altering teammates’ default experience.
Collaboration practices
Use item-level comments to keep decisions next to the work. Mention teammates so notifications route to the right people; agree on naming and status conventions so frames stay searchable.
Real-time updates reduce the need for manual refresh in many flows. For high-stakes changes, align your team on whether to confirm in chat or email outside the tool as well.
Administration
Users with administrative access can manage organization-level settings from the administration area. Day-to-day frame editing does not require admin rights; reserve admin roles for people who will own user lifecycle and governance.
Billing and subscription changes are tied to authenticated accounts with the appropriate entitlement. Document internally who approves upgrades and downgrades.
Recommended next steps
- Publish a short internal FAQ that points to this guide and your support channel.
- Run a pilot frame with a small group before a company-wide rollout.
- Review Trust & security with IT or procurement if required.
- Return to the How it works overview for a concise product summary for executives.
Create an account
Begin your rollout with a new workspace.