Admins have the capability to view all channels both open and closed. Additionally, creating a new channel is facilitated here.

Searching and Filtering

Admins can effortlessly search for and filter channels based on specific criteria. Both active and deleted channels are displayed in the list. To differentiate the state of the channel:

• Active channels are standard.

• Deleted channels feature a gray-tinted trash icon .

• Muted channels are indicated by a mute icon .

• Stopped channels display a gray-tinted stop icon .

How to Apply Filters:

1. Navigate to "Channels" in the sidebar.

2. On the top right corner, you'll find the search and filter options.

Available Filter Options:

List of Channel Actions

Create Channel

The channel types that you can create in console are:

• Community

• Live

• Broadcast

To create a channel:

1. Navigate to the side menu and select Channels.

3. A Create New Channel pop-up will appear. Fill in the required information:

   • Channel ID: Enter the ID for the channel.

   • Display Name: Provide a name that will be visible to all channel members.

   • Channel Type: Choose the desired channel type from the available options: Community, Live, or Broadcast.

   • Mute Channel: Check this option if you wish to mute all members within the channel.

5. Click Submit.

Delete Channel

The Amity Social Cloud console offers the capability to delete a channel using the following steps:

1. Navigate to the side menu and select Channels.

2. Under the Channels Management section, locate the actions row corresponding to each channel.

3. Identify and click on the trash icon associated with the channel you wish to delete.

4. Confirm the deletion by clicking on the confirmation dialogue that appears.

Managing Channel Users

To view the list of current members in the channel, select Members. Here, you will be able to manage users in the channel, such as:

• Mute or unmute a channel member

• Ban a user from the channel or unban them

• Change a user's role within the channel

• Remove a user from a channel

You will also be able to see if a user has been banned from the channel, as their user ID will be displayed in red. To unban this user, simply select on the ellipses under "Actions" and select "Unban User". Once a user has been unbanned from the channel, they will no longer appear as part of the channel member list and will be able to rejoin or be re-added into the channel.

Do note that if you remove a banned channel member, their banned status will be cleared and they will be able to join or be added back into the channel as well.

See also: Channel Ban, Muting & Unmuting Channel Users

Moderation Overview

We determine a user's moderation capabilities based on their current role.

*This role cannot be assigned to a user, but only to an Admin.

When you are routed to ASC Console after clicking Go to console in your newly created application in Amity Portal, you will be logged in as a super-admin. This is different from the global-admin and must NOT be used for normal administration tasks for the following reasons:

1. It cannot generate an Admin API access token used in making server-to-server API calls.

2. It must be reserved for operations that only a super-admin can perform such as uploading a push notification certificate.

Change User Role

You can promote a user's role from a member to a moderator. Alternatively, a community moderator can also be demoted to a member.

These are the steps to change a user's role:

1. In the left menu, select Community > Communities.

2. In the Community Management page, select a community.

3. In the community's page, click Members tab.

4. Select the member and click the Change user role button.

5. In the Change role pop-up, select the user's new role and click Save to submit.

Create Role

You can create a new role with customized permissions by following these steps:

1. in the left menu, select Users > Roles.

3. In the Create role page, provide a name for the role that you will create.

4. Customize the permissions by selecting from the list in the Permissions section on the right.

5. Click Create.

Admin Moderation Privileges

Amity Social Cloud Console provides administrators the ability to observe and control messages in channels.

Moderation tools range from automatic operations such as the blocklisting of words/phrases to controlled operations such as the manual banning and muting of users.

Blocklisting

Blocklisting is used to block certain words from being sent in Amity's Chat and Social SDK. When a word is blocklisted, anytime a user attempts to send a message, comment, or a post with that word, it will not be sent.

Contents that are moderated are:

• Messages

• Posts

• Comments

• Poll questions and answers

Contents that are not moderated include:

• Community names

• Community category names

• Channel names

• User display names

• File names

• Reaction names

• Network names

• Role names

Allow List

Amity by default prevents any link or URL from being sent. However, websites can be whitelisted so that links with that website domain can be sent.

You can enable or disable this feature.

Banning Users

There are 2 types of ban that can be performed on a user:

1. Global Ban

2. Channel Ban

Global Ban

Admins have the ability to global ban a user. When a user is globally banned, they will no longer be able to authenticate with ASC and will be forcibly removed from all their existing channels. All the globally banned user's messages will also be deleted. If the SDK has already cached the messages, they will only disappear when refreshed. Note that the global banned user's social content, such as posts, comments, and community membership, will not be removed.

The globally banned user will not be able to authenticate with Amity's network again until they have been globally unbanned.

Global-banning a user

To perform a global ban on a user:

1. In ASC Console, go to Users.

2. Select the user you wish to ban.

3. In Actions, click the ban user icon.

4. Click Confirm in the confirmation pop-up.

Global-unbanning User

To unban a user who has been globally banned:

1. In ASC Console, go to Users.

2. Select the user you wish to unban.

3. In Actions, click the unban user icon.

4. Click Confirm in the confirmation pop-up.

Channel Ban

Admins also have the ability to ban a user at the channel level. When a user is banned in a channel, unlike global ban, the user will not get disconnected but will only get an event on both user and channel level. All messages of the banned user in the specified channel will be soft deleted.

There is a real-time event telling online users in the channel that a user has been banned. Therefore, SDK can do soft delete locally and reflects the changes on to the message list right away via LiveCollection.

Channel-banning User

To perform a channel ban on a user:

1. In ASC Console, go to Channels.

2. Select the channel where the User is a member.

3. Click Members button.

4. Select the User in the channel that you wish to ban.

5. In Actions, click the ban user icon.

6. Click Confirm in the confirmation pop-up.

Channel-unbanning User

To unban a user who has been banned in the channel:

1. In ASC Console, go to Channels.

2. Select the channel where the User is a member.

3. Click Members button.

4. Select the User in the channel that you wish to ban.

5. In Actions, click the unban user icon.

6. Click Confirm in the confirmation pop-up.

General Moderation Privileges

These moderation tools are available to all admins and users with moderator and super-moderator roles

Muting and Unmuting

Moderators can mute and unmute users. When a user is muted, they cannot send messages in a channel. However, muted users will still be allowed to observe messages in a channel. The status of being muted is indefinite but is only applied at the channel level.

Banning Unbanning

Moderators can ban and unban users. When a user is banned in a channel, they are forcibly removed from the channel and may no longer participate or observe messages in that channel. All their previous messages in the channel will also be automatically deleted.

A user that has been banned from a channel can not rejoin the channel until they have been unbanned.

Moderation Level

Any frontend user of a network can be promoted into a moderator. There are two types of moderators:

1. Network Level Moderators They can moderate all posts, comments, and users in all communities across the entire network.

2. Community Level Moderators They have the same set of permissions as the Network Level Moderators but are only limited within the community wherein they are the moderator.

Moderator Permissions

Making a user an administrator allows them to:

• Create, edit, or delete roles

• Create, edit, or delete community categories

• Delete or edit communities

• Add, edit, ban, or remove community users

• Edit, review, or delete community posts

• Edit or delete community comments

• Manage posts, comments, and communities

How to promote a user to network-level moderator

To promote a user to a network-level moderator, perform these steps:

1. In ASC Console, go to Users.

2. Select the user you wish to upgrade.

3. In Actions, click the Change role icon.

4. Select Network Moderator from the user role dropdown.

How to promote a user to a community-level moderator

Broadcast Messages

The Broadcast channel is heavily adopted by corporate users who constantly promote or advertise their products, or make the announcement to drive awareness. Unlink other channel types, broadcast channels only allow admin users to send messages from Console, and everyone else in the channel will be under read-only mode. Here are the steps to follow to send a broadcast message on Console.

2. Select the broadcast channel that you created and click Broadcast Message.

3. Chose the message type, and write your message.

5. Click Broadcast.

Live Messages

Admins can join a channel and view messages being sent in real-time. They also will be able to filter messages by certain parameters, check current members in the channel and modify channel details such as tags and metadata.

Admins will also be able to broadcast messages directly in the channel.

List of Message Types

The SDK supports the sending and receiving of 5 types of messages:

Pausing Data Stream

Because the messages are being sent in real-time, sometimes an Admin will have difficulty moderating when the messages are appearing quickly. In this scenario, Admins can pause the incoming data stream so that they can take action on a message. This pause does not prevent users from sending messages in a channel but simply stops the Admin Panel from receiving new messages. Once the live message has been unpaused, Admin will see all the messages again.

Message Filters

Admins can filter what messages are to be shown on the live message stream. Currently, the SDK supports two types of filters:

1. Filter by Flagged Show only messages that have been flagged by admin or users

2. Filter by Threaded Show only messages that are parent message

View Mentioned Users

The mention feature in chat can be used to call attention to all or specific members in a channel. To view the members being mentioned in a message:

1. Go to Channels Management and select a channel.

2. In the channel's page, the Mentioned users column will list the members mentioned by a specific user in a message.

Mentioning @all members in the channel can be turned OFF:

1. Go to Settings > Feature Settings.

2. In Feature Settings page, uncheck Allow to mention everyone in channel under Events. You can check to turn ON @all mention again.

List of Message Actions

*Note: Message will still be marked as sent by user but with no text.

This feature presents a dedicated page, accessible via the Manage Users menu, then Chat activities tab . By selecting a specific user ID, admins can gain insights into the comprehensive chat activities of that user. This encompasses key metrics such as total messages sent, channels joined, and flagged messages. Further, a detailed table offers a deep dive into each user's chat interactions within specific channels, coupled with options to remove users or address flagged content. This user-centric design guarantees a streamlined experience for businesses.

Communities management

In that tab, an admin can manage entirely the communities of its network. It will be possible to use a filter by name (from the start, case insensitive), and to close (terminate) communities from this panel. The table will also contain the number of posts as a clickable number linking to the post section of the admin panel.

Community creator

By pushing the "+" button, an admin will be invited to fill a form to create communities. Communities can either be:

1. Public - any user can join the community.

2. Private - user needs to be added by the community moderator or admin.

Several options will be presented to customize the community. Once submitted, the community will be automatically visible in the table.

Categories management

Categories can be accessed from the "Categories" menu in the Communities management section. This page allows any admin to add or remove categories which are used for classifying communities.

Admin can also edit category name and avatar by selecting the category and going to the Settings page.

Posts management

This page will show the posts attached to a given context. A context can be: an external content, a community or a user. For communities and users, it will be mandatory to input the respective ID.

For example:

1. To see all the external contents of an admin's network, simply choose "Content" from the filter bar.

2. To see all the posts of a community's feed, choose "community" and input the chosen community's ID.

3. To see all the posts of a user's feed, choose "user" and input the chosen user's ID.

There are options to filter posts and reveal only ones that are flagged, as well as deleting a post if admin's deem it to be necessary.

Post creator

By pushing the "+" button, an admin will be invited to fill a form to create a post. Several options will be presented to customize the post. Admin will have to fill the "target" type and ID to be able to post.

Once submitted, the post will be automatically visible in the table. In case of having attachments, children posts will be automatically created.

The table comes with 2 sets of numbers which are clickable:

1. The "sub posts" column link will bring an admin to see the posts attached to a parent one.

2. The "comment" column link will redirect to the comment section with given context of the chosen post.

Mention in Post

When creating the post content, you can mention users to call their attention. To mention, just type the @ symbol followed by the user's display name. Typing @ will also show the user list pop-up. From the list, you can select the users that you want to mention.

In the Post management page, you can see the mentioned users in every post in the Mentioned Users column.

Comments management

The comment management section comes empty at first. To see and filter the comments, an admin must fill the context of these comments in the filter bar. It can be an external content, or a post, which for both it needs to fill the corresponding ID.

For example:

1. To see all the comments of an external content, simply choose "Content" and input the content's ID.

2. To see all the comments of a post, choose "Post" and input the chosen post's ID.

In this section too are options to filter comments and reveal only flagged ones, as well as deleting a comment if necessary.

In this table, an admin can find the following information:

• Comment id - ID of the comment

• Content - the text or comment body

• Mentioned Users - list of users that are being mentioned in the comment

• Author id - ID of the user who created the comment

• Sub-comments - link to see "sub comments", as in "threaded comments" list. Simply click on the number to reveal the new list of attached comments

• Reactions - comment reaction count

• Flags - number of flags the comment has received

• Last activity - the time stamp when a user last did something related to the comment

• Actions - flag or delete the comment

View Reactions in Post and Comment

When a user reacts to a post or comment on Amity Social Cloud, a summary of all the reactions will be displayed in the console. The reaction column will indicate the total number of users who have reacted to the specific post or comment. However, reactions to child-posts will not be included in this count.

By clicking on the reaction number, the console will open a reaction list page that displays all the reactions to that post or comment. The list will only show the reaction types that users have selected. This reaction list may differ for each post. The first column of the reaction list displays the reaction name, while the second column shows the total number of users who have used that reaction name to react.

To view the user list for a particular reaction, users can click on the number displayed in the second column. The user list page will display the usernames of all the users who have used that particular reaction type to react to the post or comment. By clicking on the user ID displayed in the first column, users can access more information about the user.

The Community tab serves as a central hub that allows you to manage all communities within your network. Here, you'll be able to easily create a new community, manage community permissions and memberships, and moderate community content such as posts and comments.

Navigate the Community Tab

Under the Community tab, you will find two pages - Categories and Communities.

Categories Page

The Categories page gives you an overview of all the categories created and which communities the categories are tagged to. Here, you can also create new categories and edit existing ones.

Categories essentially act like classifications, allowing you to tag communities that fall under the same interest area. For example, if you have 5 fitness-related communities, you can create a "Fitness" category and tag those communities under "Fitness". Tagging communities with a category enables your end users to explore other communities within the same interest area.

Read more about creating & managing categories here.

Communities Page

The Communities page gives you an overview of all communities that have been created in your network, including communities that have been deleted. To manage a community, simply select the community you want to manage, and you'll be able to manage the community's activity, memberships, and settings & permissions. You can also create a new community by selecting the "+" button on the top right.

To easily identify communities that require moderation, simply select the flag icon to filter a list of communities that contain flagged content.

View & Manage a Community's Activity

Once you've selected a community, select the "Activity" tab to view and manage all posts and comments that have been created in the community. Here, you can also schedule posts to be published, and approve or decline pending posts that require approval before it is posted onto the community's feed.

If a post has been flagged by community members, it will show you the number of times the post has been flagged; and whether the post has any reported comments. The actual content, image, and videos posted by users will be displayed here, even if the post was soft-deleted. This allows you to review flagged posts. You can then choose to either clear the flags of the posts and comments, or delete the post altogether.

View & Manage a Community's Membership

To see the community's member list, select the "Members" tab.

You'll be able to see a list of current community members, including users who have been community-banned or deleted. You can use the search feature to search for members by their user ID or display name, or filter to show only banned members. Banned and deleted users will have an icon displayed next to their User ID indicating their status.

Currently, the following community management functionalities are available on ASC Console:

• Adding a member to the community

• Changing an existing member's role in the community to another default role (either member, or moderator)

• Community banning or unbanning a user

View & Manage Community Permissions & Settings

If you want to change any of the settings and permissions of a community that was created, simply go to the 'Permissions' tab and 'Settings' tab.

Managing Posting Permissions

Under 'Permissions', you'll be able to configure the community's posting permissions.

If your community is a community that's mainly for important announcements, you can set permissions to enable "Only admins can post". This means that community members who are not moderators will not be able to create a post in the community. Read more about roles & privileges here.

If you'd like to allow members to contribute, but would like to review their posts first, you can enable "Approve member posts". When this setting is enabled, all posts created will need to be approved or declined by any moderator of the community. Only approved posts will be published in the community feed.

Do note that you can't enable both of these post settings at the same time. If both of these settings are disabled, it means that all members of the community will be able to post freely in the community feed.

Updating Community Settings

Changed your mind about making the community private? Made a typo when creating the community?

If you want to update any of the settings that were configured when a community was created, go to the "Settings" tab.

You'll be able to:

• Remove or upload a new community avatar

• Update the community's name

• Remove or update a community's description

• Change the community's category

• Mark community as an official community

• Mark community as public or private

You can also close a community, although we'd recommend that this should be an intentional decision as you won't be able to restore a deleted community.

The Amity Social Cloud console allows Super Admins to customize the permissions of Admin users. This gives organizations finer control over their admin structure and improves security by limiting actions that could lead to misuse or compromised data. Super Admins can control whether an Admin can access the following sensitive functionality:

• Access Secure Mode: Allows the Admin to access secure mode features such as generating Admin Token that Allows the admin to generate an API token for .

• Manage Admin: Allows the Admin to create new Admin accounts and configure general admins' permissions. Any new admins they create will have permissions disabled by default.

This feature enhances the admin access control on the console by introducing two different admin roles: super admin and general admin. This allows for more granular control over who has access to what features on the console.

Super Admin

The super admin role has full access to all features on the console. This includes the ability to create, edit, and delete admins, as well as manage admin tokens.

General Admin

The general admin role has limited access to the console. This includes the ability to create and edit admins, but not delete them. General admins also cannot manage admin tokens.

Manage Admin Permissions

As a Super Admin, you can configure admin permissions from the Admin Users page in the console. Each Admin user will have an associated set of permissions that you can configure, as well as their basic information.

To edit the permissions for an Admin:

1. Go to the Admin Users page.

1. Click on the "Edit name & Permissions" button for the Admin you want to configure.

1. Adjust permissions and basic information as desired.

2. Click 'Update'. The Admin user will now be restricted from performing any actions you have disabled permissions for.

Create a New Admin

As a Super Administrator, you have the authority to create new Administrator accounts. Here's how to proceed:

1. Go to the Admin Users page.

2. Click on the "Create New Admin" button.

1. Fill in the required information for the new Administrator, such as username, email, and basic information.

2. Determine and set the permissions for the new Administrator. Remember, all permissions are initially disabled for a new Administrator.

3. Once all details and permissions are correctly filled, click on the 'Create' button to create the new Administrator account.

The new Administrator account is now created. The permissions you've set will define the extent of this new Administrator's access and capabilities within the console. The Administrator will not be able to perform any functions for which you've not granted permission, thereby ensuring the secure and controlled management of your console.

Image moderation is a feature that allows all uploaded images on posts and messages to be scanned and moderated for inappropriate, offensive, and unwanted content before images are published.

To this end, we're partnering with Amazon's Rekognition AI technology to detect and moderate images that contain violence, nudity, suggestive, or disturbing content; allowing you to create a safer online community for your users without requiring any human intervention. For more information on how Rekognition works, click !

Enable Image Moderation

The following steps will allow you to enable Image Moderation for your network:

1. Log into Console

2. Go to Settings > Image Moderation

3. Toggle “Allow Image Moderation” to "Yes"

Do note that once you've enabled image moderation, you will need to also set the confidence level for each moderation category. By default, the confidence levels set are "0" for each category. Allowing any one category to be set to '0' confidence level will likely result in all images to be blocked from being uploaded, regardless of whether the image contained any inappropriate elements.

Setting confidence levels at a higher threshold is likely to yield more accurate results when it comes to detecting images for said content. If you specify a confidence value of less than 50, a higher number of false positives are more likely to be returned compared to a higher confidence value. You should only specify a confidence value of less than 50 only when lower confidence detection is acceptable for your use case.

Disable Image Moderation

To disable image moderation, simply toggle "Allow Image Moderation" to "No". Any images uploaded will no longer go through the image recognition service, and any inappropriate content will no longer be detected.

FAQ

1. Can we set confidence levels for just one category and leave the rest at '0'? Doing so will result in all images being blocked from being uploaded, even if it didn't contain any offensive or unwanted imagery. This is because Amazon Rekognition will scan the uploaded image for all categories (i.e. "Nudity", "Suggestive", "Violence", and "Disturbing) and return a confidence score for each category. If the confidence score returned is equal to or higher than the confidence level set in ASC Console, the image will be blocked. Currently, we don't have a feature to allow image moderation for just one element - but you could try setting different confidence levels for each element to see what works best for your use case.

2. What happens when an uploaded image is detected to have unwanted imagery? It depends on the confidence threshold set in ASC Console for each moderation category. For example, if your settings are ("Nudity: 99; Suggestive: 80; Violence: 10; Disturbing: 50"), based on the image uploaded, Amazon Rekognition will scan and return a confidence score for each moderation category. If the confidence score returned by Amazon Rekognition equals to, or is higher than the confidence levels set in Console for that category, ASC will block this image from being uploaded, as illustrated below:

Settings

Admin can modify various settings for the SDK from this panel. Admin can also see their SDK API and Webhook keys from this panel.‌

Webhook Settings

If the Admin wishes to set up their own webhooks, they can do so by adding a URL to the Webhook section. This will generate a secretKey for that URL webhook. Admin will also be able to delete and previous webhook URLs.‌

For more information, please have a look at our documentation on ​

Push Notifications

If the Admin wishes to set up push notifications for their SDK; they may do so by uploading a PNS certificate*. Once a push notification is active, Admin can set what events are push notifiable.

*Note: If client has not enabled Push Notifications with Amity before. Please contact us first so that we can set up the preliminary certificate credentials.

Push Notification Certificates

Admin can see what certificates are currently active for their Push Notifications. More than one certificate can be uploaded for one platform (i.e. You can have a staging and a production certificate for iOS), however, only one certificate may be active at a time per platform and/or provider.‌

Admin can upload new certificates:‌

List of Certificate Requirements

Push Notification Custom Message

For more information, please have a look at our documentation on:‌

Admin API Access Token

If you want to make request to Amity Social Cloud APIs as an admin, you will need an access token. You can get the Access token from the Admin Users Management section in console.

Once logged in as an admin, you can generate the access token with these steps:

1. Go to Settings > Admin Users.

3. Click Generate and a token will be generated in the Access Token box.

Users Management

Admins are able to view a list of all users from this tab. They will also be able to search for and filter users by certain parameters.‌

List of User Actions

In changing a user's role, admin can either promote a member to a moderator role or demote a moderator to a member role.

There is no limit to the number of moderators a community can have. This means that if there are hundreds of users in the community, all of them can be moderators. However, every community must have at least one moderator. Thus, the sole remaining moderator in the community cannot be demoted to a member.

For more information on how to change a user's role, refer to Moderation, Roles & Privileges.

Admin User Management

Admins are able to see all current Admin accounts on the SDK as well as create new Admin accounts. The username that is selected will be used as the login name. The display name is the name that users will see when the Admin broadcasts a message.‌

List of Admin Actions

Blocklist Management

Admins are able to view and manage a list of all blocked expressions from this tab.‌

Blocked expressions can either be exact or partial matches. This choice of behavior needs to be defined when an admin adds an expression to the list.‌

Admins can also set the auto mute period (in milliseconds) for when a user uses a blocked expression.‌

Adding blocked expressions via API

Adding blocked expressions in bulk can be done using the post /api/blacklist/records API. Here is the format:

{
  "regexs": [
    "expression1_string", "expression2_string", "expression3_string"
  ],
  "isMatchExactWord": true
}

Model description

Allowlist Management

Admins can view and manage a list of all allowed links from this tab.

Admin can add links to the allow list and only the links in the list will be allowed. All other links not in the list will be blocked. By default, link restriction is enabled, thus, all links will be blocked.

Feature Explanation

Network Level Push Notification Settings

The first step in using push notifications is to enable network-level push notifications settings. Please follow the steps below to achieve this.

*Only 'Super Administrator' and 'Administrator' have the ability to disable or enable this feature.

Step 1:

• In the Console page, navigate to Settings > Push Notifications

• Turn ON the Network Notification Settings toggle button.

Step 2:

Double-check that all events such as Chat, Post and Comments are correctly enabled. After the network level settings are turned ON, the notification events can be adjusted individually.

To increase the security of our admin tokens, we have enhanced the ability to generate new admin tokens with shorter expiration time and the ability to revoke admin tokens.

Generating New Admin Access Token

Previously, all generated access tokens had an expiration time of 10 years by default. From now on, the expiration time for all newly generated access tokens will be reduced to 1 year. This new enhancement only affects the newly generated tokens. So if you want a token with a shorter expiration time, you will need to generate a new token through the console.

This is not available for Super Admin.

To retrieve your current admin token:

• In the Console, go to Settings > Admin Users

• Click the ellipses (...) next to your user name to retrieve your current admin token.

• Click the Generate button to generate (create) a new token, which will invalidate the existing token.

• Click the Confirm button.

Once the new token is generated, the admin will be notified to get switched from the old token to the new token within 24 hours.

Please remember to generate a new token before it expires. Otherwise, you will get "token expired" error if you use an expired token for API calls.

Revoke Admin Token

In case the admin token has been compromised, admin users can now revoke their own admin token, and Super Admins can revoke another admin's token. Revoking tokens are done by passing the username parameter.

After revocation, that admin's token becomes invalid and the admin will be automatically logged out of Console. When that admin logs in again, a new token will be generated. The admin must use this new token for future API calls, otherwise they will receive an "Invalid token' error.

Version 4.37.0 (2023-09-21)

New Features

• Supported the ability for admins and super admins to soft delete channels directly from the console.

• Added a double confirmation pop-up to prevent accidental deletions.

• Added an option to for admins and super admins to choose whether they want to include or exclude deleted channels based on their preferences.

• Added two new options including "Show All Channels" and "Hide Deleted Channels".

Version 4.35.0 (2023-08-11)

New Features

• Introduced remove channel members feature, allowing users to remove another member from a particular channel.

Version 4.32.0 (2023-06-30)

New Features

• Updated the maximum character limit on the functionality of adding an allow list.

Version 4.31.1 (2023-05-09)

New Features

• Support the ability to get details reactions for post, comment and subpost on console.

Version 4.30.2 (2023-02-03)

New Features

• The Comments page in the console now displays flagged child comments in addition to the flagged parent comments.

Fixes

• Fixed issue where non-flagged items could have their flags 'cleared'.

Version 4.30.1 (2023-01-13)

Fixes

• Fixed issue where admin could not send broadcast message to the channel.

Version 4.30.0 (2022-12-16)

New Features

• Added functionality to support mTLS certificate.

Fixes

• Disabled the "+" button for deleted communities.

Version 4.29.0 (2022-12-02)

New Features

• Enhanced the ability to generate new admin tokens with shorter expiration time.

• Introduced the ability to revoke admin tokens.

Version 4.28.0 (2022-11-28)

Fixes

• Fixed issue with activating PNS certificates on Console.

Version 4.28.0 (2022-10-07)

New Features

• Enhanced the Usage tab in the Historical Monthly Usage table to show the total number of moderated images per billing cycle.

• Enhanced the PAYG Portal Billing Center and invoice to display any image moderation usage and billing amount that was incurred for the cycle.

Fixes

• Fixed issue where creating a broadcast with mention was not possible.

Version 4.27.0 (2022-09-23)

New Features

• In the Broadcast, Live, and Community channels all message types (text, image, file and video) are now grouped into a single event.

• In the Conversation channel all message types (text, image, file and video) are now grouped into a single event.

Version 4.26.0 (2022-09-21)

New Features

• In ASC Console, you can now download the Usage report in CSV format.

Version 4.25.0 (2022-09-09)

New Features

• Community query is now case-insensitive! You no longer have to match the case sensitivity of the community’s display name when querying for a community.

Fixes

• Fixed issue where user ID or display name weren’t appearing in the user search result, if the keyword has a special character or if it is more than 30 characters long.

• Removed the validation that prevented deleted category names from being reused when you create a new category, or when you want to update an existing category’s name. You’re now free to reuse any category name that was deleted!

Version 4.24.0 (2022-08-26)

Fixes

• SDK Upgrade

Version 4.23.4 (2022-08-11)

Fixes

• Fixed issue that limits the ability to play .mov video type

Version 4.22.4 (2022-07-29)

Fixes

• Fixed issue that prevented administrators from sending broadcast messages

Version 4.22.3 (2022-07-21)

Fixes

• Fixed issue where signing in to the portal, redirects to the console's login page

Version 4.22.0 (2022-07-15)

Fixes

• Fixed issue with message sorting in the channels management page. Messages will now be sorted according to newest created date to oldest created date

Version 4.21.0 (2022-06-20)

Fixes

• Admin will no longer be able to enable both Post Review and Admin Can Post Only settings at the same time

• Fixed alignment issue for permissions settings under Community

Version 4.20.0 (2022-06-17)

Fixes

• channelId is now optional when creating channels

Version 4.19.0 (2022-05-20)

Fixes

• Fixed issue where ASC Console was crashing upon selecting Channel Settings

• Renamed "Chat Event" to "Network Level Settings"; and "header.pns_events" to "Chat Event"

Version 4.18.0 (2022-05-22)

New Features

• Support the ability to enable and disable ‘Network Level Push Notification Settings’ via ASC Console

Fixes

• Fixed issue with avatar upload progress indicator

• Renamed "PNS Events" to "Chat Events"

Version 4.17.0 (2022-03-17)

Fixes

• Fix JavaScript sample code in Settings / Security page

• Block list / Allow list loads all data without pagination

Version 4.16.0 (2022-03-03)

Fix

• Unable to delete filter items in allow list and block list

Version 4.15.0 (2022-02-17)

New Features

• FileUploader and VideoUploader refactoring

• Remove permission to manage user feed

• Sorting of content (Channels, Livestream, Communities, Categories, Users, Roles, Posts, and Comments) by first and last created and first and last updated

Fixes

• Long file name of community avatar overlaps in UI when creating community

• Save button in Streaming details page not changed to disabled state after uploading video

• Region fallback constant set as environment variable

Version 4.14.0 (2022-02-08)

New Features

• Can enable/disable Allow list feature in console

• Roles will now show role name and role ID in the Role dropdown when updating the user’s global role

Fixes

• Category detail page ID will show community ID

• Unban button will be blocked after banning user from a channel

• Global-banned user shows unban button inside members list in Channel Management page

Version 4.13.0 (2022-01-25)

New Features

• Can set push notifications for the following events:

  1. When there’s a post sent for review in the community

  2. Notification to member when the post is approved

Fix

• Global-banned user show 'unban' button inside members list in channel management

Version 4.12.0 (2021-12-24)

New Features

• Mentioned users column in Comment Management page

• Edit the category display name and avatar

Version 4.11.0 (2021-12-09)

New Features

Push Notification

• Community member will receive a notification if the post is approved in the feed

• Moderator will receive a notification when there’s a post sent for review

Mention

• Add 'Mentioned Users' column in the Post Management page

• Create posts with mentioned user(s)

• Create posts with members of a private community

• Can search and see the list of users to select by typing the @ symbol when mentioning

Category

• Update image and name of the category

Roles

• Demote a member to a User role

• Show both role ID and role name when updating global role of the user

• Disable demoting a Moderator to a Member if there is only one remaining moderator

• Promote Member to Moderator role

• Creator/Moderators will now get “community-moderator” & “channel-moderator” roles

• Removed Community Creator privilege logics

• Add Community Moderator and Channel Moderator roles

• Now utilizing v4 API endpoints for Promote/Demote users in community

Fixes

• Changed the size of the “Mentioned User” column for “channel”

• Cannot create mention from broadcast

• Incorrect message is shown when mentioning more than 30 users

• Mentionees is not shown in 'mentioned user' column when mentioning from a community post

• Can mention non-members in a private community

• 'Mentioned user' column width is not specified

• Moderator role is not selected in the “Change Role” page for the community creator

• Disable submit button if there's no input in Push Notification message composer

• “Authorization info not found” error pops when staying in console for a few hours

Version 4.10.0 (2021-11-02)

Fixes

• Edit role and Delete role buttons are disabled for Super-moderator, Moderator, and Global-admin roles

• Unnamed file is shown after sending broadcast with file attachment, page needs to be refreshed.

• User cannot get moderator privileges even after updating to moderator role

• No error popup is shown if internet connection is lost when searching for channel

• Select members dropdown does not close after a selection

Version 4.9.0 (2021-10-15)

New Feature

• Mention users in Broadcast channel

Fix

• Text Caption not shown when sending a broadcast message with an image to a channel

• When creating a post, OK button will enable even while still uploading a video attachment

Use Server Key to securely authenticate your client with Amity Social Cloud server

With secure mode off, Amity SDK generates an access token on the client side when given a userId and apiKey. This can lead to malicious users abusing the endpoint and spying on someone else's session.

With secure mode on, an additional authentication token that is generated from your own backend server using a separate Server Key is required. You must turn on secure mode in your production system or the system will be vulnerable to such kind of attack.

How to generate a server key

Amity provides a way to get the server key easily via the ASC Console as followed:

1. Login to your ASC Console

2. Go to Setting -> Security

3. Enable secure mode via the toggle.

4. Click "Generate new server key" to generate your server key

5. Click Continue (please make sure you read the warning message and are aware of the impact)

6. The server key will be shown, please copy and securely store into your backend system. The key will only be shown once.

How to use server key to create auth token

Once secure mode is enabled and server key is generated, all client authentication request will require an authentication token and your backend server will need to make a server-to-server call, while passing server key into Amity Social Cloud server in order to get the authentication token. Please follow the following steps to generate auth token:

1. Client initiates a call to the backend.

2. For EU and US, you need to specify the region in the endpoint link. For SG, however, it is optional.

3. Receive the auth token back and find a way to pass it up from server-side to client-side and give it to the SDK.

Use your auth token in your SDK

To use auth token on the client side, please see the Getting Started guide.

How to get API key

An API key will be provided when you create the application.

1. Open Amity Social Cloud Console.

2. On the left menu, select Settings to expand its submenu.

3. Select Security.

4. On the Security page, you will find the apiKey.

Authentication

There are 2 modes of Authentication:

1. Unsecure mode

2. Secure mode

Unsecure mode

With secure mode disabled, you can connect directly to the Amity server.

2. In the Responses, you will find that the server will return an access token in the Response body.

Secure Mode

With secure mode enabled, it provides an additional layer of security because it requires server-level authentication.

2. The server will return an authentication token in the Response body.

4. In the Responses section, you will find that the server will return an access token in the Response body.

mTLS Certificate

Mutual Transport Layer Security or mTLS, is a two-way mutual authentication technique. It helps two parties to authenticate at both ends of a network if they have the correct private key. mTLS ensures that the people at both ends of a network connection are who they claim to be.

How to Enable mTLS Certificate

• In the Console, go to Settings > Security tab

• Click +Create Certificate option to create the certificate

• Specify the Certificate Name and Certificate Signing Request (CSR)

• Activate the mTLS feature

Enabling the mTLS feature is optional.

The SDK comes alongside a specialized Amity Social Cloud Console that acts as a dashboard where administrators will be able to observe and control data belonging to their network. The ASC Console provides a variety of moderation features and customizable settings for you to use to moderate your applications.

To access the console, you will need an account.

Accessing ASC Console

First navigate to the console for your application by clicking on the "Go to console" button on the "My Applications" Screen of your ASC Portal.

Getting your API Key

You can see the API key - that you'll need to connect to the client - under the "Settings/ Security" section of the console, as pictured below.

Moderation via API