> ## Documentation Index > Fetch the complete documentation index at: https://docs.begin.eu/llms.txt > Use this file to discover all available pages before exploring further. # Create custom profile fields > Add fields to people’s profiles and choose who can see, search and complete them. A Custom fields card with uniform sizes and a Required marker A Custom fields card with uniform sizes and a Required marker Use **Settings → People** to collect information your workspace needs beyond the standard profile fields. For example, add a uniform size that new hires can provide before their first day. You need **People settings** for your role. Creating custom fields and groups, and enabling **Ask new hires**, require the Pro plan. If Begin offers an upgrade, ask someone with billing access to review the workspace's plan. ## Create the field Under **Custom fields**, choose **Add → Custom field**. Enter a clear name and choose **Text**, **Number**, **Date**, **Dropdown**, **Multi-select** or **Checkbox**. For **Dropdown** or **Multi-select**, add at least one non-empty option. Use Dropdown for one answer, such as a uniform size, and Multi-select when several answers can apply. Select a group if needed and set the visibility, search and collection switches below. Save the field. Open a person in **People** and find the field on their profile. Enter a value to check that the type and instructions fit the information you need. ## Decide who supplies and sees the answer | What you need | Setting | | -------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Mark a field as required | **Required**. With **Ask new hires**, the new hire must answer before completing onboarding. | | The employee to see the field on their own profile | **Visible to employees**. Leave it off for information intended for authorised managers. | | People to be found by this field's value | **Findable in search**. Search still respects who can see the field and the person. | | A new hire to complete it during onboarding | **Ask new hires**. First turn on **Visible to employees**. | For the uniform-size example, use Dropdown, provide your actual sizes and enable **Visible to employees** and **Ask new hires**. Enable **Required** if the new hire must supply the answer before completing onboarding. Turning visibility off also removes the field from what you ask new hires. **Required** does not stop managers saving blank values on existing People profiles, and does not fill earlier gaps automatically. In the field editor, scroll below the options to find all four switches: The custom field editor with uniform sizes and Required, Visible to employees and Ask new hires switched on The custom field editor with uniform sizes and Required, Visible to employees and Ask new hires switched on ## Organise or retire fields Choose **Add → Group** to create a section. Use a field's menu to edit it, move it up or down, or change its group. Group menus also let you change the section order. Deleting a group leaves its fields ungrouped. Use **Archive** when you no longer need to collect a field but want to keep its data. Archived fields keep their values but nobody can enter new ones. You can **Unarchive** it later. Deletion is refused if the field has stored data; archive it instead. Treat changes to a field's type or choices carefully after people have answered. For a different kind of information, create a separate field so its purpose remains clear. The Custom fields list showing Uniform size and Languages in Joining the team, plus an ungrouped Locker number The Custom fields list showing Uniform size and Languages in Joining the team, plus an ungrouped Locker number **Context for an assistant answering questions about custom profile fields.** * **Scope:** definitions belong to one workspace. Viewing and editing values also follow member visibility and permissions; access to settings does not make every person's values visible. * **Limits:** dropdown and multi-select fields require at least one non-empty option. A field may have one group or no group. * **Plan boundary:** a downgrade does not delete existing definitions or values. Creating fields/groups and turning on preboarding collection are plan-gated; tidying existing definitions remains possible with permission. * **Not supported:** marking a field Required does not backfill earlier profiles. Searchability never overrides employee visibility. ## Next Read and update a person’s information. Choose what new hires complete before joining. ## Still need help? Email the Begin team and we'll get back to you. Open the AI assistant and get instant answers based on these docs.