Loading

What ActiveManage Can Do

ActiveManage is a platform for building and running business applications — the kind an organisation depends on daily, with real data, real users and real access rules.

Where to find it

Architect Panel → Data:

  • Datastores — where you describe the shape of your data

Architect Panel → Configuration:

  • Platform Modules — the capabilities enabled on this instance

What you describe, and what you get

You describe your data once as a datastore. From that single description the platform derives the database table, the create, edit and view forms, browse views, the search index, the REST API, the audit trail and the permission surface.

The practical consequence is the one that matters: adding a field is one change, not eight. In a conventionally built application the same addition touches the schema, the migration, two forms, a list view, an API contract, a test and the documentation — and the places it fails to reach are where bugs live.

The kinds of application it suits

  • Case and record management — anything where a thing arrives, is worked on by several people, and has to be evidenced afterwards.
  • Line-of-business operations — bookings, assets, projects, stock, finance.
  • Regulated work — where the audit trail, retention and access controls are as much of the requirement as the features.
  • Customer-facing portals — where the same records are visible externally under tighter rules.
  • Multi-tenant products — one installation serving many isolated organisations.

What comes as standard

Authentication and single sign-on, two-factor, permissions to row and field level, audit logging with tamper evidence, retention and disposal, search, document generation, e-mail and SMS, scheduled tasks, an API, and reporting. None of these are projects; they are settings.

That is the actual argument for a platform. Any competent team can build a booking system; the twelve months afterwards are spent building everything in that list around it.

What it is not

Being straightforward about this saves everybody time. It is not a website builder, not a general programming environment, and not the right tool for something whose value is a novel algorithm or an unusual interface. It is for applications whose shape is records, rules, people and process — which is most business software, but not all of it.

You are not locked out of code

Where a screen genuinely needs to be bespoke, it can be. The point is that the other ninety screens do not, so the effort goes where it is actually warranted.

Worked example

A housing association replaces three systems and a set of spreadsheets. Repairs, tenancies and compliance inspections become datastores; the contractor portal is the same records under different permissions; the regulator's evidence request is answered from the audit log. Nothing in that list required custom code, and the parts that did — a scheduling screen the team wanted laid out a particular way — were built as exceptions rather than as the norm.

Recommendations

  • Model your data before designing screens. Everything derives from it.
  • Check what is already standard before building it.
  • Reach for custom code as an exception, not as the starting point.
  • Be honest about fit — the platform is excellent for record-shaped problems and mediocre for others.