Quick summary

1. Run HuduAssetLayoutTransfer.exe

2. Choose the source and destination layouts

3. Pick merge behavior for matching assets

4. Review each destination field in the mapping wizard

5. Confirm the final plan and run the transfer

What This Tool Does

- Transfers asset data from one Hudu layout into another

- Supports field-by-field mapping through the GUI

- Lets you use constant values for required destination fields

- Supports SMOOSH to combine multiple source fields into one destination field

- Can normalize or strip HTML from rich text when needed

- Supports structured AddressData destination mapping

- Supports ListSelect destination mapping, including optional creation of missing list items

- Can merge or skip when a likely matching asset already exists in the destination

- Relinks supported related records such as passwords, uploads, articles, and photos

What Gets Carried Over

- Any source asset fields you choose to map

- AssetTag relations, converted into direct relations where applicable

- Related passwords

- Related procedures

- Related articles

- Attached uploads

- Public photos

- Related photos *

*Photo relinking requires Hudu 2.41.0 or later.

Requirements

- PowerShell 7.5.1 or later on Windows PC

- A Hudu base URL

- A Hudu API key

- An existing source layout and destination layout

Quick Start

1. Launch the tool

Run HuduAssetLayoutTransfer.exe.

The tool opens a GUI window and a terminal window. The terminal is mainly there for logging and troubleshooting.

2. Enter your Hudu connection details

Provide your Hudu URL and API key.

3. Choose the source and destination layouts

Pick the layout you are moving from and the layout you are moving to.

You will then get a confirmation step to review or change the selection.

4. Choose merge behavior for matches

If an incoming source asset appears to match an existing destination asset, you can choose how the tool should behave.

You can also optionally rename the source layout after the transfer is complete.

5. Decide whether to archive the original source assets

This is usually recommended once you are confident the transfer plan is correct.

6. Review field mappings

If the source and destination layouts already line up closely, the tool may offer a direct transfer path.

Otherwise, you will work through the field mapping wizard one destination field at a time.

Merge Modes

When a source asset appears to match a destination asset, choose one of these behaviors:

- Merge-FillBlanks: destination wins; source only fills missing values

- Merge-PreferSource: source wins; destination acts as fallback

- Merge-Concat: keeps both values for text-like fields and chooses a winner for non-text fields

- Skip: do not transfer the source asset if a match is found

Use Merge-Concat when you want to preserve both sets of notes or descriptive text. Use Merge-FillBlanks when the destination is already your source of truth.

Field Mapping Workflow

Each destination field is reviewed in the GUI. For every field, choose one mapping mode:

- Source Field: map from one source field

- Constant Value: always write the same literal value

- SMOOSH: combine multiple source fields into one destination field

- Skip: leave the destination field unmapped

The mapping editor also shows a live snapshot of:

- Configured destination fields

- Pending destination fields

- Skipped destination fields

- Mapped source fields

- Unmapped source fields

Use Back and Next to move through the review loop. Back discards any in-progress edits for the current field unless that field was already saved earlier.

Standard Source Mapping

This is the most common path: pick a source field and optionally enable Strip HTML.

Use Strip HTML when moving from rich text or embed-like source fields into plain text destination fields.

Constant Mapping

Use this when a destination field should always receive the same value.

This is especially useful for required destination fields that have no good source equivalent.

ListSelect Mapping

For ListSelect destination fields, choose a source field and define which source values should map to which destination list items.

This is helpful when the source data is inconsistent and needs to be normalized into one controlled list.

Example:

- Source values like floor, ground, or dirt can map to destination option ground stuff

- Source values like sunny or sunshine can map to solar stuff

Matching is case-insensitive and uses first-match-wins behavior.

If the destination list may be missing values, enabling Add missing list items is usually the right choice.

AddressData Mapping

AddressData fields can be mapped by parts:

- address_line_1

- address_line_2

- city

- state

- zip

- country_name

The tool builds the destination address object only when at least one address component is present.

SMOOSH Mapping

SMOOSH lets you combine multiple source fields into one destination field. It is usually most useful for RichText, Heading, or other notes-style destinations.

Example rich text output:

Serial Number:
9JD2NLAL4
Notes:
This is a good computer (link)

Example plain text output:

9JD2NLAL4; This is a good computer; John 
https://huduurl.huducloud.com/a/computerslug

Per-Job Settings

After field mapping, the tool asks a few follow-up questions depending on how your plan is configured.

$includeblanksduringsmoosh (default - $false) -

Includes empty values when building SMOOSH output.

$includeLabelInSmooshedValues (default - $true)-

Prepends the source field label before each SMOOSHed value.

$excludeHTMLinSMOOSH (default - $false)-

Strips HTML and flattens SMOOSH output into cleaner plain text.

$includeRelationsForArchived (default - $true)

Preserves relations even when the related object is archived.

How Matching Works

Before creating a destination asset, the tool checks whether a likely match already exists.

A source asset is treated as a likely match when:

- It belongs to the same company as a destination asset, and

- The names are the same, or the destination name starts with or ends with the source name

Very short names are intentionally not matched too aggressively.

This matching logic helps prevent accidental duplicates while still allowing flexible merge behavior.

Review, Outputs, and Logs

Before the transfer runs, the tool shows a final summary of the mapping plan, including:

- Direct mappings

- Constants

- SMOOSH target and source count

- Skipped fields

- Merge behavior

- Archive preference

After the transfer, the tool writes a timestamped JSON results file such as:

- transferresults_YYYYMMDD_HHMMSS.json

The console output also includes field-level and relation-level progress messages to help with troubleshooting.

Troubleshooting Tips

Plain text fields showing HTML

Enable Strip HTML on the specific field mapping, especially when the source field is RichText, Heading, or Embed-like content.

ListSelect values not landing where expected

Double-check the whenvalues mapping and remember that matching is case-insensitive and uses the first matching destination option.

Email fields look messy

Make sure the destination field is typed or labeled as an email field so the email cleanup logic can normalize the value correctly.

Address casing looks odd

The helper logic normalizes common US state names and country variants such as US, USA, and United States.

Tips

- Prefer matching destination field types when possible

- Use constants to satisfy required destination fields that have no good source value

- Use SMOOSH for notes-style destinations rather than trying to cram several inputs into a single normal field

- For plain text destinations, consider both Strip HTML and excludeHTMLinSMOOSH=$true

- Start with a small test layout or a small company subset before running a large migration

---

Changelog

- v0.3 - Initial public draft of the layout-switching documentation, November 19, 2025

- v0.5 - Added merge-on-match options, February 23, 2026

- v0.6 - Added constant fallback values and combined relation handling on match, March 3, 2026

- v0.8 - Added password, photo, public photo, and upload reattribution, March 4, 2026

- v1.0 - Finalized GUI, added forward,back buttons, and field indicator panel.

I wanted to post a guide for our self-hosters for migrating from the old AssetTag format-
While many of you have likely already made the switch, there's likely a few that haven't yet. Thankfully, doing this is super-easy.

it is always a good idea to kick off a backup first

First, you'll need to access your container host, which is most likely a linux host. It doesn't matter whether you access a headless box via ssh or a fancy desktop environment.

You'll just need to start a new terminal session (with a user in the docker group or root), and run the below command to start the process-

docker exec -it -u 0 $(docker ps --filter "name=app" --format "{{.ID}}") bin/rake convert_asset_tags:to_new_format

If you're nervous or have a large instance, you can tee the output to a file for later review with the below one-liner. This just results in everything being logged to a file named something like- tags_result_1775068117.txt

docker exec -it -u 0 $(docker ps --filter "name=app" --format "{{.ID}}") bin/rake convert_asset_tags:to_new_format 2>&1 | tee "tags_result_$(date +%s).txt"

You'll see a stream of text while this is working through the process. It's quite fast, but you'll see exactly how many fields have been converted to the new AssetTag format (and how many already were in this format)

It's always good to have the latest + greatest! Let us know if you have any questions!

See link in Community Repo

=========================================================

WHAT THIS SCRIPT DOES

---------------------

The script signs in to Microsoft Azure, reads your Hudu API key and Hudu site URL from Azure Key Vault, calls the Hudu API, and builds one Central Knowledge Base article with inventory counts. Each run refreshes that article's HTML content.

The KB article includes:

- Executive Global Summary: fixed list of resource types (companies, assets, layouts, KB articles, passwords, expirations, folders, password folders, procedures, networks, websites, IP addresses, rack storages/items, VLANs, VLAN zones) with Active / Archived / Total where the API supports it.

- Per-company totals and a full Company Resource Breakdown (every company, every listed resource type, zeros included), plus per-company archived sum and grand total rows.

- Asset detail sections (by layout globally, by company, by layout per company).

- Data Retrieval Errors: any API/list failures and notes (for example duplicate KB article titles).

- Article selection: the script looks up the KB article whose title exactly matches $CentralReportArticleName (default "Central Audit Report"). If found, it updates that article. If several articles share the title, it updates the one with the latest updated_at timestamp (tie-break: higher article id) and records a warning in Data Retrieval Errors listing the other ids. If not found, it creates a new article with that title.

- Documentation, that lives in the comment block at the top of: hudu_central_audit_report.ps1

REQUIREMENTS (READ CAREFULLY PLEASE)

-----------------------------

1) PowerShell 7 or newer is required. Do not use Windows PowerShell 5.1 for this script. The script file includes #Requires -Version 7.0 so it will refuse to run on 5.1.

2) Run PowerShell 7 "As Administrator" for the session where you will execute the script. Some environments need this for module installs or policy; use an elevated window for consistency.

3) Entra ID + Azure Key Vault secrets. This script does not embed your Hudu API key or URL in plain text. You sign in with the Azure Az PowerShell modules; the script then calls Get-AzKeyVaultSecret.

Note: "Entra ID" (Azure AD) is only how your admin may sign you into Azure. The script itself reads named secrets from a Key Vault. In Entra you can create secrets under: Azure Portal(Entra ID) → Key vaults → your vault → Objects → Secrets.

4) Your Azure account (or the account you use with Connect-AzAccount) needs at least Get and List on the secrets used for Hudu URL and Hudu API key. The script does not write any Key Vault secrets for the report.

CONFIGURATION YOU MUST EDIT (IN THE SCRIPT)

--------------------------------------------

Open hudu_central_audit_report.ps1 and find the section:

CONFIGURATION - EDIT THESE VALUES

Set these to match your Key Vault and secret names:

$AzVault_Name = "your-key-vault-name"

$AzVault_HuduApiKeySecretName = "AUDITAPI"

(Secret value = your Hudu x-api-key. ~ You can get this in your Hudu instance as a Super-Admin from Admin > API Key.)

$AzVault_HuduBaseDomainSecretName = "AUDITURL"

(Secret value = your Hudu base URL or hostname. Examples that all work after normalization: hudu.com | https://hudu.com | https://hudu.com/ )

$CentralReportArticleName = "Central Audit Report"

(Exact KB article title the script creates or updates. Must match the article name you want in Hudu.)

-ReportDetailLevel

Controls how much data the script includes in the KB article.

You can choose from:

Executive (default)

Includes global summary and data retrieval errors only.

Smallest payload. Use if the KB article fails to render (500 error) due to size.

Full

Includes all tables: global summary, company totals, company resource breakdown, assets by layout, assets by company, assets by layout per company.

Best for complete auditing. May hit Hudu HTML size limits on very large instances (500+ companies).

Compact

Includes global summary, company grand totals, assets by layout (global), and assets by company.

Skips heavy per-company breakdown tables. Good balance of detail and size.

Example usage: -ReportDetailLevel Compact

Full audit example: -ReportDetailLevel Full

CREATING KEY VAULT SECRETS (ENTRA ID STEPS)

------------------------------------------

1) Azure Portal → Key vaults → select your vault.

2) Objects → Secrets → Generate/Import.

3) Name: use the same name as in the script (e.g. AUDITAPI, AUDITURL).

4) Secret value: paste the Hudu API key or URL/domain as appropriate.

5) Save.

DUPLICATE KB ARTICLE TITLES

----------------------------

Avoid duplicate titles. If more than one article uses $CentralReportArticleName, the script updates the most recently updated article (see Article selection above) and logs a warning with the other article ids. Consolidate or rename duplicates in Hudu so only one central report article remains.

OPTIONAL SWITCHES

-----------------

-DryRun

Connects and gathers data but does not POST or PUT the KB article. Prints what it would do.

-VerifyEndpoints

After validating Hudu credentials, calls each API path the report uses and prints row counts. Does not update the KB article. Use this to confirm API access and pagination behavior.

-ReportDetailLevel

Controls how much data the script includes in the KB article. Choose from:

Executive (default):

1. Smallest payload. Use if the KB article fails to render (500 error) due to size.

2. Includes global summary and data retrieval errors only.

Full:

1. Includes all tables: global summary, company totals, company resource breakdown, assets by layout, assets by company, assets by layout per company.

2. Best for complete auditing. May hit Hudu HTML size limits on very large instances (500+ companies).

Compact:

1. Includes global summary, company grand totals, assets by layout (global), and assets by company.

2. Skips heavy per-company breakdown tables. Good balance of detail and size.

Examples -ReportDetailLevel Compact

Full audit: -ReportDetailLevel Full

NORMAL RUN (UPDATE OR CREATE THE ARTICLE)

-----------------------------------------

1) Install PowerShell 7+.

2) Open PowerShell 7 as Administrator.

3) Install Az modules if prompted (script may install Az.Accounts and Az.KeyVault for the current user).

4) Edit the CONFIGURATION section in hudu_central_audit_report.ps1.

5) Run:

pwsh -File "C:\path\to\hudu_central_audit_report.ps1"

For a full (largest) report in one run:

pwsh -File "C:\path\to\hudu_central_audit_report.ps1" -ReportDetailLevel Full

(Use your actual path to the script folder.)

6) Sign in to Azure if Connect-AzAccount appears.

7) Wait for "Updated central KB article" or "Created central KB article" action in Hudu.

EDGE CASES AND TROUBLESHOOTING

------------------------------

- Empty or wrong AUDITURL: fix the secret value; the script normalizes scheme and trailing slashes but must end with a resolvable host.

- Empty AUDITAPI: validation fails with a clear error.

- Access denied on Key Vault: grant your identity Secret Get and List on the vault (or on those secrets via RBAC).

- "Endpoint verification" failures: run with -VerifyEndpoints and read which path failed; often, pagination or permissions on a specific resource type.

- If you rename the central article in Hudu but not in the script, the script will create a new article using $CentralReportArticleName.

- If the KB article fails to render (500 error) on very large instances, try -ReportDetailLevel Compact or Executive to reduce payload size. Try increasing your rate limit if you run into this issue. Additional resources may be required if the API rate limit change does not address your issues.

You can find the latest copy of the executable (Windows 10+ | x86_64 only) in our main GitHub repository here: ITGlue-Hudu-Migration (file calledITGlue-Hudu-Migration-GUI.exe)

Or directly download the executable: https://github.com/Hudu-Technologies-Inc/ITGlue-Hudu-Migration/raw/refs/heads/main/ITGlue-Hudu-Migration-GUI.exe

What's new:

You can now add the Hudu node directly as a tool inside your n8n workflows.

Just:

• Specify the target entity

• Define the allowed operations

Everything else is handled by the node.

You can install n8n-nodes-hudu here: https://www.npmjs.com/package/n8n-nodes-hudu

For more information, see this Reddit Post!

This script is a small activity log explorer for Hudu.

Instead of writing individual Where-Object filters every time you want to answer questions like:

• “Show me everything where record_type is Article”

• “Which user did update actions?”

• “What activity happened from this IP?”

• “What details were included in those events?”

…it pulls a sample of activity logs, lets you pick an attribute, then pick a value, and prints the matching logs back out in a readable, story‑like format.

Why This Exists

Hudu activity logs are powerful — but digging through them manually gets old fast.

This helper turns raw activity data into an interactive, explorable audit tool that’s fast, readable, and human‑friendly.

How to Run

Open a new pwsh7 session on your windows device and perform one of the following:

the Oneliner [Ninja-Style]

irm 'https://raw.githubusercontent.com/Hudu-Technologies-Inc/Community-Scripts/refs/heads/main/Administration/Auditing-Activity-Logs/Audit-ActivityLogs.ps1' | iex

Clone+Start [Samurai-Style] (requires git scm installed)

git clone https://github.com/Hudu-Technologies-Inc/Community-Scripts; cd .\Community-Scripts\Administration\Auditing-Activity-Logs; . .\Audit-ActivityLogs.ps1;

Download-Extract-Run [Ashigaru-Warrior-Style]

Invoke-WebRequest https://codeload.github.com/Hudu-Technologies-Inc/Community-Scripts/zip/refs/heads/main -OutFile Community-Scripts.zip; Expand-Archive -Path .\Community-Scripts.zip; cd .\Community-Scripts\Community-Scripts-main\Administration\Auditing-Activity-Logs; . .\Audit-ActivityLogs.ps1;

After submitting required infos, You’ll see:

1. A numbered list of attributes → pick one

2. A numbered list of values → pick one

3. Matching activity entries printed in green

Common Use Cases

• Audit a single action type
  “Show me all delete actions”

• Track changes to a specific record type
  “Only Passwords activity”

• Investigate suspicious behavior
  “Everything from IP x.x.x.x”

• User troubleshooting
  “What did this user do around that time?”

• Client / company review
  “What activity happened under company X?”

How It Works

1. Pulls Activity Logs

You start with a set of activity log records
(whatever Get-HuduActivityLogs returns in your environment).

2. Builds Drilldown Attributes + Values

The script scans all properties present across the returned objects and builds a lookup table like:

• action → { create, update, delete, … }

• record_type → { Article, Asset, Password, … }

• user_name → { Mason, Cameron, … }

• company_name → { Acme Inc, Contoso, … }

• ip_address → { 10.0.0.5, 203.0.113.42, … }

This lets you browse the dataset without memorizing field names.

3. Interactive Selection

You are prompted to choose:

1. An attribute to filter by

2. A value for that attribute

No manual filtering required.

4. Human‑Readable Output

For each matching activity log entry, the script prints a friendly summary including:

• Who did it (name → email fallback logic)

• What action occurred

• Which record (type + name)

• Company context

• Source (browser / app + OS)

• IP address

• Details (if present)

• Timestamp (formatted_datetime)

The result reads more like an audit trail than raw JSON.

Menu Reference

Attribute Selection

This answers the question:

“Which field do you want to filter on?”

Common examples:

• record_type — Article vs Asset vs Password

• action — create / update / delete

• user_email / user_name

• company_name

• ip_address

• app_type

Here are some ways you can easily add such flags and apply them to suit your organizations needs-

Flags and FlagTypes can help tighten focus around items in Hudu that need special care, more attention, review or revision. Being a powerful feature set for organization and notation, it's a good capability to have a handle on as a Hudu user, administrator or power-user.

Notes on FlagTypes

FlagTypes can be applied to a variety of objects in Hudu

• Articles

• Networks

• Ip Addresses

• VLAN Zones

• Assets

• Companies

• Procedures

• Rack Storages

• Passwords

While these are general categories that something might fit in, how you use them is up to you.

The best part? You can pick from a variety of colors to represent any of your FlagTypes

You might have a FlagType named 'Needs Attention' or 'Under Review' for quality assurance purposes with the color Orange

You might have a FlagType named 'Handle With Care' or 'Special Case' for special cases or edge cases with the color Pink

You might have a FlagType named 'Mason' or 'Cameron' to define ownership of article or object with the color Green

You might have a FlagType named 'Invoices' or 'Cash on Delivery' to define characteristics of a company with the color Purple

You might have a FlagType named 'Deprecated' or 'EOL' to flag objects that aren't going to be in use much longer with the color Blue

You might have a FlagType named 'In-Service', 'Checked-Out' or 'Not-In-Service' to flag objects that are in a special state with the color Grey

Notes on Flags

Flags represent the individual attribution of a flagtype to an object For example, if you have a FlagType named 'Needs Attention' or 'Under Review' for quality assurance purposes with the color Orange, you might apply that to 6 passwords, 2 companies, and an asset. This would result in 9 new Flag objects. Flag objects can be revoked or changed at any time and any single object can have one, none, or several distinct/unique flagtypes attributed to them.

Firstly, you'll need to load the prerequisite helper functions with this one-liner (using pwsh7+), then you're ready to roll. Start a new pwsh session and run:

irm 'https://raw.githubusercontent.com/Hudu-Technologies-Inc/Community-Scripts/refs/heads/main/Administration/Flags-And-Flagtypes/Prerequisites.ps1' | iex

You can run this command from an existing powershell session start a new one Run-Command Dialog (Start+R / ❖+R) and typing 'pwsh'

If all the prerequisites are met (updated HuduAPI module and Hudu 2.40.0 or newer), you'll get a nice green message indicating that you're ready to go- If not, you might try with elevated permissions or after upgrading your hudu instance.

Let's go through some scenarios. Of course, you can and are encouraged to modify these scenarios to better suit your needs

Scenario 1: we want to flag all assets that haven't been updated since $flagDate

First, you'll need to set your $flagDate variable. This can be any date that you think any given asset should have been updated since. Most date formats are valid to set here, but to keep the day and month sections from being conflated with one another, the below formats are good. We give preference to international formats here.

$flagDate = '26 Jan 2026 15:56'
# $flagdate = '26-01-2026 15:56'
# $flagdate = '26/01/2026 15:56'

with your flagdate variable set, we can compare the dates, assign some flags, and take a closer look at these stale assets as a team-

$allAssets = Get-HuduAssets | Where-Object {Compare-DateStrings -a $_.updated_at -b $flagDate}
$staleAssetesFlag = Select-OrCreateFlagType -description "Flag all assets not updated since $flagDate"
$allassets | ForEach-Object {New-HuduFlag -flagTypeId $staleAssetesFlag.id -flagableType "asset" -flaggableId $_.id}

Scenario 2: we want to flag all articles that have less than 100 characters in Length

For this snippet, we'll want to set what we think is an acceptable minimum length (in characters) for articles. Any articles shorter than this, we will flag for review-

$minimumAcceptableLength = 100

$shortArticles = Get-HuduArticles | Where-Object {"$($_.content)".length -lt $minimumAcceptableLength}
$shortArticlesFlag = Select-OrCreateFlagType -description "Flag all articles with less than 100 characters"
$shortArticles | ForEach-Object {New-HuduFlag -flagTypeId $shortArticlesFlag.id -flagableType "article" -flaggableId $_.id}

Scenario 3: lets get a handle on weak passwords!

Weak passwords should be under a magnifying glass, since they can create a major security gap. In this example, we'll set a variable for minimum password length and for minimum unique characters used.

$minimumpasswordLength=8
$minimumCharsUsed=6

Once you've defined what you think are acceptable minimum values for passwords, you can 'flag away'

$weakPasswords = get-hudupasswords | Where-Object {"$($_.asset_password.password ?? $_.password)".length -lt $minimumpasswordLength -or ("$($_.asset_password.password ?? $_.password)".ToCharArray() | Select-Object -Unique).Count -lt $minimumCharsUsed}
$weakPasswordsFlag = Select-OrCreateFlagType -description "Flag all weak passwords with either less than $minimumpasswordLength chars, or fewer than $minimumCharsUsed different chars"
$weakPasswords | ForEach-Object {New-HuduFlag -flagTypeId $weakPasswordsFlag.id -flagableType "password" -flaggableId $_.id}

Scenario 4: we want to flag all procedures that have too-few tasks/steps

If your organization has some procedures that might need to be evaluated, this can be a great starting point Firstly, we'll define what we think is an acceptable minimum number of steps or tasks a procedure should have

$minimumAllowedSteps=2

And we can then apply that to all the procedures in Hudu with the snippet below

$weakProcedures = Get-HuduProcedures | Where-Object {$_.total -le $minimumAllowedSteps}
$proceduresFlag = Select-OrCreateFlagType -description "Flag all procedures that have $minimumAllowedSteps or fewer tasks/steps"
$weakProcedures | ForEach-Object {New-HuduFlag -flagTypeId $proceduresFlag.id -flagableType "procedure" -flaggableId $_.id}

Scenario 5: we want to flag all rack storages that are underutilized (less than X% capacity)

First, we'll need to define what we consider to be underutilized (as percent utilization). In this example, we'll suppose 10% or lower constitutes an underutilized rack storage, but you can change this as best suits your needs

$minimumUtilization=10

Then, we're ready to flag some rack storages

$underutilizedRacks = Get-HuduRackStorages | Where-Object {[int]($_.utilization) -le $minimumUtilization}
$racksFlag = Select-OrCreateFlagType -description "Flag all rack storages that are underutilized (less than $minimumUtilization% capacity)"
$underutilizedRacks | ForEach-Object {New-HuduFlag -flagTypeId $racksFlag.id -flagableType "rack" -flaggableId $_.id}

Scenario 6: we want to flag external networks so that they will be recognized and handled with care

This one is pretty straightforward and doesn't require any user-defined variables. We're just selecting for external networks. It can help to make these external networks easily identifiable so they may be handled with extra care

$externalNetworks = Get-HuduNetworks | Where-Object {[int]($_.network_type) -eq 1}
$externalNetworksFlag = Select-OrCreateFlagType -description "Flag all external networks"
$externalNetworks | ForEach-Object {New-HuduFlag -flagTypeId $externalNetworksFlag.id -flagableType "network" -flaggableId $_.id}

Scenario 7: lets flag all publicly shared articles so that we don't update them with sensitive info by mistake

This is a pretty big one, especially if you have many internal and external articles to differentiate.

$publicArticles = Get-HuduArticles | Where-Object {$_.enable_sharing -or $_.share_url}
$publicArticlesFlag = Select-OrCreateFlagType -description "Flag all publicly shared articles"
$publicArticles | ForEach-Object {New-HuduFlag -flagTypeId $publicArticlesFlag.id -flagableType "article" -flaggableId $_.id}

I'm personally not a fan of the cards integrations in Hudu, so I created a script that:

• Pulls users from ms365 graph based on specific distribution groups such as "All company employees" or whatever you use. Allowing you to add any graph data to the user asset in Hudu. Currently includes name, email, Phone number, Teams number, Title, Department.

• Adds a list of all collaboration groups, security groups, mail-enabled security groups and distribution groups to the user asset.

• Can easily be built upon the n8n flow to add more elements to the user asset.

It's something that comes up now and again and is easier than ever.

This helpful little snippet is in our Community Repo, or can be invoked with this oneliner, below.

 pwsh  -NoProfile -ExecutionPolicy Bypass -Command "irm 'https://raw.githubusercontent.com/Hudu-Technologies-Inc/Community-Scripts/main/Administration/Listifying-Text-Fields/Listify-Text-Field.ps1' | iex"

First, you can select any layout that has a TextField

Then, you can simply select the field you would like to make a new ListSelect field for as a replacement. All of your data will be carried over to this new field and all unique values will be available in a new list assigned to it!

After you select the desired field you'd like to change over, you'll be asked to confirm-- and if something doesn't seem right, you can exit with CTL+C key combination

After you confirm by hitting enter, it will get to work.
The script will:

• grab all unique values for this field in your selected layout

• create (or update) a new list containing unique values

• add this field to your chosen layout

• copy over values from source field to new list field for all assets in layout
  
  And that's it! You may want to confirm things are looking as-expected, and then wrap up by removing the original field. Conveniently, this script opens up the administrative page for your chosen layout and the global asset view for your chosen layout.
  

Happy Listifying!

Maybe you want a standard structure something like:

• SOPs

  • Adminstrative

  • New User Setup

  • Network Request Forms

• Troubleshooting

  • Network

  • Servers

  • Printers

Using Script to create a templated KB Folder Structure Across Companies

This guide shows what you will need:

• How to create the Key Vault

• How to create the two secrets

• How to use them in your script

• A minimal working example

============================================================

This script utilizes Azure Key Vault keys for security so it's not storing your actual API key information.

Create Azure Key Vault

1. Create the Azure Key Vault

Step 1 — Open Azure Portal

Go to: https://portal.azure.com

Search for Key Vaults → click Create.

Step 2 — Required fields

Project details:

• Subscription: your subscription

• Resource group: choose or create one

Instance details:

• Key Vault name: must be unique (example: Hudu-Automation-Vault)

• Region: pick your region

• Pricing tier: Standard

Access Configuration:

• Permission model: Role-based access control (RBAC) (Required for PowerShell scripts)

Networking:

• Public access: Enabled

• Allow all networks (for now)

Click Review + Create → Create.

2. Give Yourself Permission

In your new Key Vault → left menu → Access Control (IAM) Click Add → Add role assignment

Select role:

• Key Vault Secrets User (read secrets only, recommended) OR

• Key Vault Administrator (full access — only for setup)

Add your Azure user

Save

You now have permission to read secrets from PowerShell.

3. Create the Two Required Secrets

Inside your Key Vault → Secrets → Generate/Import.

Secret #1 — Hudu API Key

• Name: HuduAPIKey

• Value: paste the API key from Hudu Path in Hudu: Admin → API Keys

Click Create.

Secret #2 — HuduBaseURL

• Name: HuduBaseURL

• Value example: https://docs.yourcompany.com

OR: docs.yourcompany.com

(Both work — the script normalizes it.)

Click Create.

Run the Script

4. Use the Script (Clean Version)

Enter your Azure Vault Key and Hudu URL at the top of the script before running. Select either options 1 or 2 after company listings.

Option 1 will apply your folder creation to all companies. Option 2 will apply your folder creation to the company IDs you enter.

If you select option to please format your IDs as follow: 1,2,4,5,etc

How to create folders:

Here's an example of what you would type:

testing 0 
 testing 1 
 testing 2 
 testing 3 
  testing 4 
  testing 5 
   testing 6 
    testing 7 
    testing 8 
testing 9 
 testing 10 
  testing 11 

This creates the following structure:

• testing 0 (root)

  • testing 1

  • testing 2

  • testing 3

    • testing 4

    • testing 5

      • testing 6

        • testing 7

        • testing 8

When done follow confirmation messages, and accept the creation.

The script will then create the folders, and silently remove any credentials used(API, Domain, Azure Secrets, etc).

You can view the script here: