Learn some of the key terms used in the SpecFuse.
Daniel Baylis
24 October 2019


4thPortal is the company that created and runs SpecFuse. We are based on the Gold Coast in Australia. We've been operating since 2013.

4thPortal was previously named after our call center management system, UltimateCSR.


All users in SpecFuse are grouped into organizations.

An organization is created when a user first creates their account. Any additional users they invite will become part of that organization.

Organization Admin

An organization admin is a special user permission that allows users to invite additional users, and modify or delete existing users accounts. They can also update the billing details for the organization's subscription, such as credit card details and plan.

Organization admins can also grant the same privilege to other users.

Product Strategy

A Product Strategy is plan for who your application is for and what problems it solves.

When you create a project in SpecFuse, you can also choose to create a product strategy. SpecFuse makes this easy by asking questions to guide you through the process.

Once completed, you product strategy can easily be viewed by everyone on the project team. This makes it easy for you and your team to stay clear on the project vision and keep heading in the right direction.

Project Admin

A project admin is able to:

  • Modify the project and product strategy;
  • Add or remove users to the project team;
  • Manage releases;
  • Configure integrations; and
  • Delete projects.

You will automatically be an admin on any projects you create. As a project admin you can also grant the same privilege to other users on the project team.

Project Team

Only users on the project team can access a project.

Project admins can add or remove users from a team, as well as change their role between admin or team member.


Requirements are short, specific statements that describe an aspect of functionality. They can be found within specifications.

Typically, a specification is made up of multiple requirements.

Requirements must describe the outcome required in clear, specific terms. They do not need to include any background or justification as these are covered elsewhere in the specification.


A specification is a description for a specific feature or aspect of functionality in an application. They are referred to as specs for short. Specs can include background information and capture details on the type of purpose of the changes they describe.

Ideally, specs will contain multiple requirements that break the needs down into clear, specific detail.

© 4thPortal 2019-2022.
Powered By SwiftDesk.