Asset Registration Rules

A registration rule decides where a newly installed forwarder lands. Without one, a new asset arrives ungrouped and carries whatever the default policy is. With one, it joins a static group on arrival and inherits that group's policy immediately.

This matters most at the two moments a fleet grows fastest: an initial rollout, and everything provisioned afterwards. A machine that sits ungrouped for a week is a machine collecting under settings nobody chose, and nothing tells you it happened.

Registration rules are per environment, and the group you can target must already exist in that environment. See Groups and Policies.

How do I create one?

Go to app.stairwell.com and sign in.
Open Settings, then the Asset registration tab under Environments.
Select the environment the rule belongs to.
Select + Create registration.
Give it a name and choose a target static group.
Select Save registration.

The environment you pick in step 3 decides the list of groups you get in step 5. If the group you expect is missing, you are almost certainly in the wrong environment rather than missing a group.

How do I change or remove one?

Same screen, and the environment selector matters just as much.

Open Settings, then Asset registration, and select the environment holding the rule.
Select the ... icon under Actions.
Choose Edit to change the name or the target group, then Save registration. Choose Delete to remove the rule.

Editing a rule does not move assets that already registered. It changes where future arrivals land. Machines that came in under the old rule keep the group they were given, so a correction to a rule usually needs a second step: move the affected assets by hand, or accept that they are grouped by when they arrived rather than by what they are.

What should I read next?

Groups and Policies, for what a group and a policy actually control.
Forwarder Deployment, for the rollout this runs during.
Assets, for the record a registration rule is acting on.