> For the complete documentation index, see [llms.txt](https://spaceone-dev.gitbook.io/admin-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spaceone-dev.gitbook.io/admin-guide/getting-started/domain-admin.md).

# Domain Admin

## Sign-in

**STEP 1:** Drive to domain of **SpaceONE** on browser and type given ID and Password as domain admin.\
**(**E-mail received from the Root Account has stated detailed the connection methods; Single Sign On(SSO),  ID/PW, or Google Oauth2**)**

![](/files/-MTseeG_fuoFnVMz1h1c)

## Create Project Group

All cloud resources **MUST** belong to a certain project for management purposese. You can grouping any projects with Project Group. \
Domain Admin creates the project group based on the company's management policy.

{% hint style="info" %}
**Note>** General User **(Project Admin)** creates projects only under project group with permission to manage cloud resources.   
{% endhint %}

**STEP 1:** Drive to menu **`Project`** at the top menu bar and click **`+ Create Group button`** of the panel.

![](/files/-MTsek_SesDSaibryzba)

**STEP 2:** Type project group name (**sample case: Landing Zone**) and Click Confirm.

![](/files/-MTsepNnRNE4HLydxj0K)

**STEP 3:** Type project group name (**sample case: Services**) and click Confirm.

![](/files/-MTseuv3e8HPbZu0mOV0)

**STEP 4:** Type project group name (**sample case: Business Support Systems**) and click Confirm.

![](/files/-MTsf1qMsQqKmelSapDu)

**STEP 5:** Check all 3 project groups have created a tree on the left menu.

![](/files/-MTsf7phUxRmE-v35-sK)

## Create User

Create general users and assign the project groups to the created user. General users can access only the project group to which they are belonged to.

**STEP 1:** Drive to menu **`Identity > User`** at the top bar. 

![](/files/-MTsfEBx8bj3-nDYf0y0)

\
**STEP 2:** Click **`+ Add`** button to add a domain Admin user.

![](/files/-MTsfK9qV2GmJlHv0ytV)

**STEP 3:** Fill out all required fields and click **`Confirm`** button once finish.

![](/files/-MTsfSHNkf2mCCQ9EoFY)

**STEP 4:** Drive to Project and click **MEMBER** icons at right next to **`+ Create Project`** button.

![](/files/-MTsf_2aOibL5WghTk1M)

**STEP 5:** Click **`+ Add`** button and select members to add to the project group on the list at the pop-up window.

![](/files/-MTsfgDuJ8DuH-EVb1QL)

**STEP 6:** Click **`Confirm`** button when you finish to all members and set their role as project admin.

![](/files/-MTsflOojuBqOevI3jJr)

**STEP 7:** Check all selected members have registered as project members.

![](/files/-MTsfrsEsrWJJYTUQdfi)

## Cloud Resource Collectors

**Cloud Resource Collector** (a.k.a **CRC**) is a plugin that collects cloud resources across platforms such as AWS, Google Cloud, Azure, CRC is set by Domain Admin only.

**STEP 1:** Drive to Menu **`Plugin > Collector`**and Click **`+ Create`**button.

![](/files/-MTsfxlbHQEpyWrkTjGd)

### **Create AWS EC2 Collector**

**STEP 1:** Select **AWS-ec2** plugin and Click **`+ Create`** Button. 

![](/files/-MTsg39tzun8VNtylkdd)

**STEP 2:** Please, fill out all required fields and select drop downs for each steps (**add tags** is optional) and Click **`Confirm`** button to create **AWS EC2 collector**.

![](/files/-MTsgXMIZfm1hGIUGSTa)

### **Create AWS Cloud Services Collector** 

**STEP 1:** Select AWS**-cloud-services** plugin and Click **`+ Create`** Button. 

![](/files/-MTsgcuOhQ6kYDmjQxpY)

\
**STEP 2:** Please, fill out all required fields and select drop downs for each steps (**Add Tags** is Optional) and Click **`Confirm`** button to create **AWS Cloud Service Collecto**r.

![](/files/-MTsgi8tzN-YVngp_S5i)

### **Create AWS  Trusted Advisor Collector** 

**STEP 1:** Select **AWS-trusted-advisor** plugin and Click **`+ Create`** Button. 

![](/files/-MTsgofAU7zZxwZePdxL)

**STEP 2:** Please, fill out all required fields and select drop downs for each steps (**add Tags** is optional) and Click **`Confirm`** button to create **AWS Trusted Advisor collecto**r.

![](/files/-MTsh0uwRLNCGfae9O7U)

### **Create AWS Health Dashboard Collector** 

**STEP 1:** Select **AWS-personal-health-dashboard** plugin and Click **`+ Create`** Button. 

![](/files/-MTshAMGYh9fJdk847AQ)

**STEP 2:** Please, fill out all required fields and select drop downs for each steps (**add Tags** is optional) and Click **`Confirm`** button to create **AWS Health Dashboard collector**.

![](/files/-MTshEdnth7kcOgX1Iis)

### **Create Monitoring Metric Collector** 

**STEP 1:** Select **monitoring-metric-collector** plugin and Click **`+ Create`** Button. 

![](/files/-MTshKjevRgR-lY_kA8a)

**STEP 2:** Please, fill out all required fields and select drop downs for each steps (**add Tags** is optional) and click **`Confirm`** button.

![](/files/-MTshmuM6d33Qw76CO-L)

**FINAL STEP:** Check all created collectors on the collector list.

![](/files/-MTshsB-iSmG9TAsfzDU)

## Set collection schedule

The schedule is to set the collection time so that the collectors run the jobs periodically to collect cloud resources.

**STEP 1:** Click the **Schedule** tab on the bottom(detail) page of the selected collector.

![](/files/-MTsi0j2kgTkAx5HbH76)

**STEP 2:**  Click **`+ Add`** button; Fill out Name and Time zone, and Select Schedule Frequency and then Click **`Confirm`** button once the schedule setting is finished. 

{% hint style="info" %}

1. Set '**Hourly schedule**' which runs everyday at selected hour 
2. Set '**Repeat Every \***' which runs every given intervals in seconds, minutes or hours.
   {% endhint %}

![](/files/-MTsi8z3GiCTvcOB8eZh)

\
**STEP3:** Check whether the collector schedule is registered on the collector.

![](/files/-MTsiECxz0UCAaEBXynD)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://spaceone-dev.gitbook.io/admin-guide/getting-started/domain-admin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.