The Community Profile screen is the central hub for branding and technical communication settings.
Users with the Community Administrator or Community Features role can access this by navigating to the Administration module > Settings > Profile tab.
Customization & Branding
This section controls the visual identity of your Unimarket environment.
Name: Used to define the Community name. The "Name" appears on official documents (e.g. Purchase Orders).
Display Name: The "Display" name is used for internal site branding on the dashboard. The Display name is generally used if you name the site something internally. The community name will be used if this is not provided. The Display name is not used on POs or any communications to suppliers.
Community Code: The community code used during integration and for the site URL.
Banner: A JPEG/PNG image (50px high, max 500px wide) that appears at the top of every page. The graphical banner is used to customize the look of the community and appears at the top of all community pages.
Menu Color: Allows you to match the system's navigation bar to your organization's branding.
Currency: Defines the currency of your community.
Dashboard Messaging (Description)
You can communicate directly with your buyers on the homepage using three tools:
Community Message: General text or welcome messages. That will appear at the top of the community's homepage
Alert: Highlighted text for urgent or critical instructions. Often used if there are special instructions buyers need to see.
Links: Direct URLs can be inserted to display on the homepage and used to provide links to documents or webpages, such as 'Purchasing Guidelines' or internal support.
Logos
Communities can assign different logos that will be included in specified communications sent via Unimarket.
You can specify different logos for different contexts:
Printable: Appears on PDFs and Purchase Orders.
Email: Displayed in the header of system-generated emails.
Public: Shown on the supplier registration screen.
This determines the "From" address for various system notifications. You can use one Default address for everything or specify unique addresses for different functions:
| Category | Purpose |
|---|---|
| Approvals | Where approval request notifications are sent from. |
| Invoicing | Handles invoice error and receipting notifications. The email would be sent to the suppliers' invoice contact if the invoice that was created came in and was not submitted (i.e. rejected). A notification email would be sent to the buyer if an invoice came in for an order that has not been received. |
| Orders | The address from which Purchase Orders are sent to suppliers. |
| Supplier Forums | The email address that supplier invitations for registration and comments to the supplier are sent from (other than RFx communication). This is also the email that comments posted by the supplier and notifications when suppliers complete their registration are sent to. |
| Integration | Receives alerts if web service messages fail due to connection issues. |
Integration Credentials
This section provides the technical identifiers needed to link Unimarket with your Finance/ERP system.
Integration Username: This is the username used with sending integration messages to Unimarket and is a system generated identifier.
Integration Password: A community-set, encrypted password.
Community UUID: The unique system identifier for your specific community.