> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/org/general/add-viva-engange-community.md).

# Add Viva Engange Community

Create a Viva Engage community with owners

### Description

Creates a Viva Engage (Yammer) community with the given name, visibility and directory listing, and adds the named owners. The API user that creates the community can be removed from the resulting Microsoft 365 group once another owner exists.

### Location

Organization → General → Add Viva Engange Community

**Full Runbook name**

rjgit-org\_general\_add-viva-engange-community

### Details

| Property         | Value                               |
| ---------------- | ----------------------------------- |
| Version          | 1.0.1                               |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.10) |
| Schedulable      | no                                  |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * User.Read.All
    * *Resolves each owner UPN to a user object when CommunityOwners is provided*
  * Group.ReadWrite.All
    * *Finds the new community's M365 group, reads its owners and adds new owners*
  * GroupMember.ReadWrite.All
    * *Adds each new owner as group member via /groups/{id}/members/$ref*

### Parameters

#### CommunityName

Name of the community, up to 264 characters.

| Property            | Value            |
| ------------------- | ---------------- |
| Required            | true             |
| Default Value       | Sample Community |
| Type                | String           |
| Portal display name | Community name   |

#### CommunityPrivate

A private community is visible only to its members.

| Property            | Value              |
| ------------------- | ------------------ |
| Required            | false              |
| Default Value       | False              |
| Type                | Boolean            |
| Portal display name | Private community? |

#### CommunityShowInDirectory

Lists the community in the Viva Engage directory so people can find it.

| Property            | Value              |
| ------------------- | ------------------ |
| Required            | false              |
| Default Value       | True               |
| Type                | Boolean            |
| Portal display name | Show in directory? |

#### CommunityOwners

Sign-in names of the owners, separated by commas.

| Property            | Value  |
| ------------------- | ------ |
| Required            | false  |
| Default Value       |        |
| Type                | String |
| Portal display name | Owners |

#### removeCreatorFromGroup

Takes the API user that created the community out of the group, as long as at least one other owner exists.

| Property            | Value                               |
| ------------------- | ----------------------------------- |
| Required            | false                               |
| Default Value       | True                                |
| Type                | Boolean                             |
| Portal display name | Remove the API user from the group? |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/automation/runbooks/runbook-references/org/general/add-viva-engange-community.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.