Hello there!

Need Help? We are right here!

miniorange Support~
miniOrange Email Support
success

Thanks for your Enquiry.

If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com

Search Results:

×

Every object created by hand ends up a little different.

One admin fills in the department. Another leaves it blank. A third puts the user, or the new laptop, in the wrong OU. Over time the directory fills with users, groups, computers and contacts that look alike but follow no standard, and every report, group rule and audit has to work around it.

Helpdesk needs a short form, not the whole directory. A long form with every attribute invites mistakes, and handing out wider access just so someone can create an object is more than the job needs.

miniOrange Object Templates let you design the form for each task. You choose the fields, set defaults, mark what is required, hide or lock the rest, and assign the template to the roles that should use it. The same builder works for every object type.

From blank form to standard form

The same four steps for a user, group, OU, computer or contact.

1
Step 01

Design

Pick the object and whether the template creates or modifies it. Add steps and sections and drag in the fields you need.

2
Step 02

Configure

Set a label and default value for each field, and mark it required, editable or hidden. Add any LDAP attribute as a custom field.

3
Step 03

Preview and assign

Walk through the form in a full-page preview, then assign the template to the roles that should use it.

4
Step 04

Use it

Those roles see your form when they create or modify the object. Workflows can use the same templates for user actions.

Four steps from a blank Active Directory form to a standard object template

See object templates on a live domain

Build a template for a new hire, a laptop or a vendor contact and watch the form change for the role you assign it to. Bring the fields your team fills in today.

Book a Demo Request a Quote

Key Features of AD Object Templates

One builder for every object type, with the fields, defaults and roles you choose.


Five object types

Five object types

Templates for users, groups, organizational units, computers and contacts, so every kind of object you create follows a standard.

Create and modify templates

Create and modify templates

Separate templates for creating a new object and for changing an existing one, each managed on its own page.

Drag-and-drop builder

Drag-and-drop builder

Add fields from a searchable palette, arrange them in wizard steps and titled sections, and set each field to full or half width.

Field settings

Field settings

Change a field's label, set a default value, and mark it required, editable or hidden. Defaults pre-fill the form, so the person only types what is different. The fields AD needs to create the object stay required.

Custom attributes

Custom attributes

Add any LDAP attribute from your directory as a field, with its own default value.

Full-page preview

Full-page preview

Walk through the finished form before anyone uses it.

Additional Features



Role assignment

Role assignment

Assign a template to roles, so helpdesk, HR, desktop support and other teams each get the form built for their job.

Workflow ready

Workflow ready

Create and update user actions in workflows pick a template, so approved requests use the same form.

Permissions and audit

Permissions and audit

Separate permissions cover view, create, edit and delete for each object type. Template names are unique per type, a save is refused if someone else changed the template meanwhile, and every template action is written to the audit log.



Object templates in practice

Design the form without code
Give each role its own form
Every template change is on the record
Computers and contacts get the same standard

Design the form without code

The builder has a searchable palette of fields on one side and the form on the canvas. Group fields into wizard steps and titled sections, drag them into place, and click a field to change its label, default value and options. It is the same builder for users, groups, OUs, computers and contacts.

  • Wizard steps and sections, each with its own title
  • Searchable field palette
  • Full or half width for every field
  • Editable, hidden and required options per field

Give each role its own form

When you save a template, give it a name and a description, and choose the roles that should use it. A role you assign a template to uses it whenever its members create or modify that kind of object, so HR sees the new-hire form, desktop support sees the computer form and helpdesk sees the short one. This is how you delegate user creation without handing out wider access.

  • One template can serve several roles
  • Create and modify templates are assigned separately
  • User templates can also be picked in workflow actions

See how roles and delegation work

Every template change is on the record

Viewing, creating, editing and deleting a template are all written to the audit log. Each object type has its own permissions, so the people who design templates can be a small group.

  • View, create, edit and delete are separate permissions
  • Audit events cover fetch, create, modify and delete
  • A save is refused if the template changed since you opened it

Computers and contacts get the same standard

Computer objects and contacts need standard values too. A computer template can predefine the OU, the managed-by owner and the description, so every new machine account is created the same way. A contact template makes it easy to create a contact in Active Directory and keep contact management consistent for partners, vendors and other external people, with the name, email, phone and company filled in from one form.

  • Computer templates for a standard OU, owner and description
  • Contact templates for partners, vendors and external staff
  • Create and modify templates for each, assigned to roles
  • Same builder, preview and audit as every other template

Real situations this is built for

Three places a template saves time and mistakes.


Every new hire is set up the same way

Every new hire is set up the same way

HR creates accounts for new joiners and the directory should look the same for each one. A new user template makes user provisioning in Active Directory repeatable.

  • Build a user creation template with the fields HR needs
  • Set the OU and common values as defaults
  • Assign it to the HR role, so every new user comes from one form
New laptops land in the right OU

New laptops land in the right OU

Desktop support adds machine accounts, and they should never end up in the default container.

  • Build a computer creation template
  • Set the OU, owner and description as defaults
  • Assign it to the desktop support role
Vendor and partner contacts stay consistent

Vendor and partner contacts stay consistent

Contacts for vendors and partners are created by different people and recorded in different ways.

  • Build a contact creation template with name, email, phone and company
  • Make a contact modification template for updates
  • Assign both to the teams that maintain contacts

Frequently Asked Questions

What are AD object templates?

Which objects can I make templates for?

Can I add my own fields?

Who uses the templates?

Can I preview a template before using it?

Who can create or edit templates, and is it recorded?

  

x

*
*



*






 Thank you for your response. We will get back to you soon.

Please enter your work email-id

Want To Schedule A Demo?

Request a Demo