Feature request for custom UserEntry fields of type TextInput, Password Input, Option selection #9

New Issue

michael · 2026-01-19T18:31:13Z

michael commented

2026-01-19 18:31:13 +00:00

Originally created by @chupsuymang on GitHub.

Hi,

I have a feature requests that I really would need in Setup Manager.

Very often I have to make custom Input upon system setup such as selecting certain configuration type's, other text, password or checkbox inputs.

Currently we do this post Setup within the Users session through another product and I would really like to get this included in the actual enrollment experience for the tech to select instead of depending on the enduser to select the correct stuff.

I think it would be very useful, if one could create custom Inputs which can be further processed as variable in shell commands as example,
such as a script or cli application, getting passed the value as a %CustomOptionInput% or $CustomOptionInput.

The way of configuration I would think would not be much different than those inputs for building or computer name possible already, just using custom names and maybe a label. Kind of like example below.

<key>userEntry</key> <dict> <key>customVariableName</key> <dict> <key>label</key> <string>My Custom Option Box</string> <key>options</key> <array> <string>Config Option 1</string> <string>Config Option 2</string> <string>Config Option 3</string> <string>Config Option 4</string> <string>and so on...</string> </array> </dict> </dict>

And maybe similar for a Checkbox or Text input.

Originally created by @chupsuymang on GitHub. Hi, I have a feature requests that I really would need in Setup Manager. Very often I have to make custom Input upon system setup such as selecting certain configuration type's, other text, password or checkbox inputs. Currently we do this post Setup within the Users session through another product and I would really like to get this included in the actual enrollment experience for the tech to select instead of depending on the enduser to select the correct stuff. I think it would be very useful, if one could create custom Inputs which can be further processed as variable in shell commands as example, such as a script or cli application, getting passed the value as a %CustomOptionInput% or $CustomOptionInput. The way of configuration I would think would not be much different than those inputs for building or computer name possible already, just using custom names and maybe a label. Kind of like example below. `<key>userEntry</key> <dict> <key>customVariableName</key> <dict> <key>label</key> <string>My Custom Option Box</string> <key>options</key> <array> <string>Config Option 1</string> <string>Config Option 2</string> <string>Config Option 3</string> <string>Config Option 4</string> <string>and so on...</string> </array> </dict> </dict>` And maybe similar for a Checkbox or Text input.

michael added the enhancement duplicate labels 2026-01-19 18:31:13 +00:00

michael closed this issue

2026-01-19 18:31:13 +00:00

michael commented

2026-01-19 18:31:13 +00:00

@scriptingosx commented on GitHub:

duplicate #24

@scriptingosx commented on GitHub: duplicate #24

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#9