Setup Hub & Module Settings
Everything that decides what words the module uses and what rules it enforces now lives in one place. Setup holds the catalogue — categories, status labels, custom fields, fieldsets, depreciation profiles — and Settings, beside it, holds the switches the module reads while it runs. Models and Locations are the two exceptions: they are tabs of the Assets register itself, because you reach for them while looking at equipment rather than while configuring the module.
ams/settings)
— one full-width Assets page. The catalogue tabs come first, straight after
General, and the module's switches follow them. They used to be two sibling
pages, Setup and Settings, sitting next to each other in the sidebar and describing
themselves in almost the same words; if you did not already know which was which you
had to open both. Settings was also listed under the platform's own
Settings → Components; it no longer is, because these are the switches
this module reads while it runs rather than platform configuration. Every old direct
address still works — the catalogue pages did not move, and ams/setup
now opens this page.
Why these became tabs
Categories, custom fields and depreciation profiles used to have their own permanent lines in the sidebar. They no longer do, and that is deliberate: a sidebar that lists every page stops being navigation and becomes a table of contents. These are rooms you enter occasionally and on purpose, usually all in one sitting when you are setting the module up or adding a new class of equipment — so they belong together on one page rather than scattered down a menu you read every day.
What is on the hub
You only see the tabs you are allowed to open. The hub itself needs nothing more than basic Assets access, and then shows each room only to somebody who holds that room's own permission — so it can never offer a door that will not open.
| Tab | What you set there | Needs |
|---|---|---|
| Categories | The classes of equipment you own, and the custom-field schema and defaults each one carries. | Assets: Categories |
| Status Labels | Your own status vocabulary, and crucially which of those statuses allow equipment to be handed out at all. | Assets: Entries |
| Custom Fields | Extra fields beyond the built-in ones — anything your business tracks that the product does not know about. | Assets: Entries |
| Fieldsets | Named groups of those fields, so a category can adopt a whole set at once. | Assets: Entries |
| Depreciation Profiles | The reusable write-down rules a category or an asset can be put on. | Assets: Entries |
| Settings | The module's own rules — the whole of the next section. | Assets: Settings |
The Settings page — nine groups
Settings changes what the module requires of everybody, not just what it shows you. A threshold you raise this afternoon silently changes what every endorsement from tomorrow needs. That is why it has its own permission rather than riding on ordinary register access.
General
| Setting | What it decides | Default |
|---|---|---|
| Asset tag format | The pattern new tags are generated from, including how many digits are padded. | AST-000001 style |
| Default status label | What a newly registered asset starts as. | — |
| Default condition | The condition a new asset is assumed to be in. | — |
| High-value threshold | The amount above which equipment is treated as high value — used by the data-quality score, and available to your own policies. | ₱50,000 |
| Require a photo on high-value assets | Whether an expensive record is expected to carry a photograph. | Off |
| Overview cache | How long the dashboard's figures are held before being recomputed. | 5 minutes |
| Export row limit | The largest spreadsheet any report or queue will produce. | 5,000 rows |
| Data-quality batch size and low-score threshold | How many rows one bulk step handles, and the score below which a record counts as poor. | 50 / 60 |
| Comment sort order and who may be mentioned | How the comment stream on an asset is ordered, and which people can be @-mentioned in it. | Newest first / everyone |
Custody
| Setting | What it decides | Default |
|---|---|---|
| Endorsement and transfer numbering | The reference format the paperwork is numbered with, per year. | END-2026-0001 style |
| Acceptance window | How many days somebody has to confirm receipt before they are chased. | 3 days |
| Default return-by period | How long a handover runs by default. Zero means no automatic due date. | 0 (none) |
| Approval threshold | The value above which a handover must be approved before it can be released. Zero means never. | 0 (never) |
| Always approve data-bearing equipment | Require approval for anything that holds data, whatever it cost. | On |
| Require a caretaker for non-person holders | Equipment issued to a room, branch or project must name somebody answerable. | On |
| Caretakers must accept the role | Being named a caretaker is a request, not an assignment. | On |
| Require a condition on handover | Nobody hands equipment over without recording the state it is in. | On |
| Allow accepting on somebody's behalf | Whether a third party may sign for a recipient at all. | On |
| Return inspection policy | Inspect everything coming back, only exceptions, or nothing. | Everything |
| Who may hold equipment | Which kinds of holder are offered: people, branches, departments, projects, rooms, other assets, outside parties. | All of them |
| Overdue grace period | How long past the due date counts as merely late rather than overdue. | 0 days |
| Repair custody drift automatically | Whether the nightly consistency check may correct what it finds, or only report it. | Off — report only |
| Default responsibility terms | The wording frozen onto an endorsement when the category supplies none of its own. | — |
Ticketing
How fault reports connect to the Helpdesk. Whether the bridge is on at all; which ticket type and which team a raised ticket goes to; the subject line it gets; which severities raise a ticket automatically and which mark the equipment unavailable; who is asked to confirm a repair actually worked; whether a failed confirmation reopens the ticket; and the status names used when equipment goes in for repair or is reported lost. Covered in full on Issues & Helpdesk Tickets.
Maintenance
| Setting | What it decides | Default |
|---|---|---|
| Work order numbering | The reference format work orders are numbered with. | WO-2026-0001 style |
| Capitalisation threshold | The repair cost above which the spend is treated as adding value rather than as an expense. | 0 |
| Warranty reminder window | How many days before a warranty ends the reminder goes out. | 30 days |
| Maintenance reminder window | How many days before scheduled maintenance falls due. | 3 days |
Audits
| Setting | What it decides | Default |
|---|---|---|
| Audit cadence | How often equipment should be counted, in days — the value pre-filled when scheduling. | 90 days |
| Reminder and escalation windows | How early a campaign is chased, and how long overdue before it is escalated. | 3 / 3 days |
| Campaign numbering | The reference format campaigns are numbered with. | AUD-2026-0001 style |
| Evidence policy | Photograph everything, only exceptions, or nothing. | Exceptions only |
| Require a photo on a discrepancy | A finding without a picture is one person's word. | Off |
| Independence required | Whether the person holding an asset may audit it. | Off |
| What to do when something is found elsewhere | Correct the register as you count, ask first, or only report it. | Ask first |
| Audit schedule | The recurring counts that open themselves — scope, frequency and who leads. | — |
Accounting
| Setting | What it decides | Default |
|---|---|---|
| Default book, and the list of books | Which set of figures is used unless told otherwise, and what other sets exist. | Corporate |
| Currency | What money is reported in. | The company's |
| Default method and convention | How a write-down is calculated, and how the first and last part-periods are treated. | Straight line, full month |
| When depreciation starts | From the purchase, or from the day the asset was put into service. | Placed in service |
| Estimate review month | Which month of the year useful lives are asked to be re-confirmed in. | December |
| Approval before posting and self-approval | Whether a period must be approved before it is posted, and whether the person who prepared it may approve it. | Required / not allowed |
| Automatic locking | How many days after posting a period is closed to further correction. | 30 days |
| Prepare next period automatically | Whether the monthly job leaves a draft run waiting on the 1st. | On |
| Run numbering and calculation batch size | The reference format for a period, and how much is calculated per step. | DEP-2026-00001 / 200 |
Disposal
| Setting | What it decides | Default |
|---|---|---|
| Disposal numbering | The reference format disposals are numbered with. | DSP-2026-00001 style |
| Approval threshold, and finance approval above it | The value above which a disposal needs signing off, and whether finance specifically must sign. | ₱50,000 / required |
| When data must be destroyed | Always, never, or only for equipment that holds data. | Both rules apply |
| Allowed disposal methods | Which routes out of the register are offered: sale, donation, trade-in, scrap, recycling, return to lessor, write-off, transfer out. | All of them |
| Require evidence | Whether a disposal must carry documentation before it can complete. | On |
| Status after disposal | What the asset's status becomes once it leaves the register. | — |
| Sanitization reminder gap | How often a pending data wipe is chased. | Every 3 days |
Notifications
How early the return and acceptance reminders begin, how long an overdue return waits before it is escalated, and who the escalation goes to on top of the people directly involved. The reminders themselves are described on Automation & Reminders.
API
The largest page of results an integration may ask for in one request (100 by default), plus a statement of the access scopes this module makes grantable. See Connecting Other Systems.
Setting the module up, in the right order
-
Statuses first
Nothing can be handed out until at least one status allows it. Decide your vocabulary before anything else, because everything downstream refers to it.
-
Then locations and categories
Locations are where things are; categories are what things are. Both are referred to by almost every report and every audit scope, so getting them right early avoids a bulk re-classification later.
-
Custom fields, then fieldsets, then attach them to categories
In that order — a fieldset is built from fields that already exist, and a category adopts a fieldset that already exists.
-
Models, once you know you will buy the same thing twice
A model is worth creating the moment a second unit of it arrives.
-
Depreciation profiles, if finance will use the module
Only needed if you intend to depreciate. Attach them to categories so new equipment inherits one.
-
Settings last
By now you know your own vocabulary, so the thresholds and policies have something real to refer to. Start permissive and tighten — a threshold set too strictly on day one mostly teaches people to work around the module.