Learn about the different types of Boards and how you can use them to add or contribute to discussions, tickets, or alerts, or write reviews, to stay informed and collaborate. Learn about using markdown in Board content such as discussions and comments.
In the developer portal, a board is a forum where users with similar interests or responsibilities can share information, report issues, and participate in discussions.
The standard user interface includes the following boards:
The platform also includes, for each user, a user Dashboard. The Dashboard is an aggregate of all the boards that the user is following.
For instructions to access different types of boards, refer to the table below.
To access this type of board... | Follow these steps... |
---|---|
User's Dashboard | In top navigation bar, click Dashboard. |
App board | My Apps > specific app > at top right, choose app version > on left menu, click Board. |
Group board | My Groups > specific group > on left menu, click Board. |
API board | My APIs > specific API > at top right, choose API version > on left menu, click Board. |
Depending on the nature of a specific board, it might contain one or more of the following board item types, which fall into two categories:
In general, any Board item relating to a basic resource on the platform, such as an app or API, is posted to the Board for that resource. A specific user's Board only includes Board items relating to that user, not to the apps and APIs the user is associated with, since the user's associations might change. An individual user can view Board items for an app or API by going to the applicable app or API's Board..
For specific Board item types, and the Board each is posted to, refer to the table below.
This Board item type... | Is posted to this Board/Boards... |
---|---|
Alert | API, app |
API Access Request (Contract request) | API, app |
Discussion | The resource the discussion is on (API, app, or group) |
Group Membership Invitation | Group, User (for invited user) |
Review | The resource the review is on (API, app, or group) |
Ticket not associated with a specific app | API, User (for user who wrote the ticket) |
Ticket associated with a specific app | API, app |
Note: Reviews are a Board item type but do not show up on the Board for a resource; instead, they are visible on the Details page for the resource (app or API).
You can add reviews for the following resources:
For instructions, see How do I add a review?
If moderation is turned on in the version of the developer portal you are using, the content you add has to be approved, usually by an Administrator, before it's published.
When you add content and it's pending approval, it's visible only to you and to users who are authorized to approve it. When it's published, it's visible to all who have visibility of the resource, such as an app, API, or group.
If moderation is turned on in the version of the developer portal you are using, the content you add has to be approved before it's published.
In most cases, users with the following roles can approve board items:
Note: The above is the default behavior. In some cases, behavior might be modified by a custom workflow.
An authorized user can add a discussion to the board for an app, API, or group:
An authorized user can write a ticket on an app or API:
An authorized user can write an alert on an API. To write an alert, you must be an API Admin.
Note: In addition to user-generated alerts, some alerts are generated by the platform based on certain events.
An authorized user can:
Note: Depending on the platform's moderation settings, the discussion is either published immediately or goes through an approval process during which time it's visible only to you and to users who are authorized to approve it.
Depending on the platform's moderation settings, the ticket is either published immediately or goes through an approval process during which time it's visible only to you and to users who are authorized to approve it.
Depending on the platform's moderation settings, the alert is either published immediately or goes through an approval process during which time it's visible only to you and to users who are authorized to approve it.
To add a comment on a discussion, ticket or alert, just click into the Write a Comment box to expand the canvas.
Type the comment, and then click Post.
If markdown is supported for comments on the platform, you'll see the markdown icons above the comment box. For more information, see How do I use markdown in my discussions, tickets, alerts, reviews, or comments?
You can write a review for any app, API, or group you have access to.
You must be logged in to write a review.
For instructions, see How do I add a review?
You can write a review for an app, API, or group.
Depending on the platform's moderation settings, the review is either published immediately or goes through an approval process during which time it's visible only to you and to users who are authorized to approve it.
Note: If someone comments on your review, you receive a notification email.
The Dashboard is a configurable information system that helps users stay informed about relevant activity in the developer portal. Each user's Dashboard is an aggregate of information relating to all the boards that the user is following, including boards for apps, APIs, and groups. It's like a newsfeed.
When you log in to the platform, the first page that displays is your personal Dashboard page. If you're on another page, you can get to your Dashboard by clicking the link in the top navigation bar.
An individual user's Dashboard includes information such as:
For more information on notifications and newsfeed functionality, see How do I enable or disable email notifications, How do notifications work?, and What information is displayed on my Dashboard?
There are a couple of ways you can help make sure you have relevant information on your Dashboard, without having so many messages that you miss important ones. You can:
You can also choose to receive news updated by email.
If markdown is enabled for discussions, tickets, alerts, reviews, or comments, the platform supports adding formatting, and possibly images, links, and files, with a subset of a flavor of markdown called CommonMark. For more information, see http://spec.commonmark.org/0.19. For information on the specific subset that's supported, use the help link in the developer portal (see below) and/or review the topics in this document.
You can also review the examples page.
Help in the developer portal: For help with the markdown, including examples, click the help button in the document window when you're adding a discussion, ticket, alert, review, or comment with markdown support. The inline help page shows the markdown you can use and also what it will look like to users.
When you create discussions, tickets, alerts, or reviews, or comment on an existing discussion, ticket, or alert, there are two text formats that might be available:
If markdown is enabled for the resource, you'll see icons above the textbox where you enter the main content. The example shown below is for Discussions.
The first icon allows you to upload a file into your markdown; the file itself is not displayed, but users see a clickable link and can download the file. The second icon allows you to upload an image, which will be displayed inline in your content.
To enter markdown comments, type the text, adding markdown as you go. To see how the markdown will look to viewers, click Preview. To continue writing, click back to the Source tab.
For information on how to add specific formatting, click the ? icon below the Tags line. You can also review the topics below:
For information on how to upload files and add images for your markdown, see How do I add a file to my discussion, ticket, alert, review, or comment? and How do I add an image to my discussion, ticket, alert, review, or comment?
If you feel you should be able to use markdown, but the feature is not enabled, contact your Site Admin.
The platform's markdown feature supports six levels of heading. Use one hash sign (#) for Heading 1, a second for Heading 2, and so on. Make sure there's a space between the character and the heading text. See below.
For this style... | Use these characters... | Like this... |
---|---|---|
Heading 1 | # | # Heading 1 text |
Heading 2 | ## | ## Heading 2 text |
Heading 3 | ### | ### Heading 3 text |
Heading 4 | #### | #### Heading 4 text |
Heading 5 | ##### | ##### Heading 5 text |
Heading 6 | ###### | ###### Heading 6 text |
To add inline bold, italics, or strikethrough to your copy, use the formatting shown below.
Just add the required characters before and after the copy you want to format.
For this style... | Use these characters... | Like this... |
---|---|---|
Bold | **Text** | **This is bold text** |
Bold, alternative | __Text__ | __This is bold text__ |
Italics | *Text* | *This is italic text* |
Italics, alternative | _Text_ | _This is italic text_ |
Strikethrough | ~~Text~~ | ~~This is strikethrough text~~ |
To indent one level, just use the greater than character as shown below.
For this style... | Use these characters... | Like this... |
---|---|---|
Indented once | > | >This is indented copy |
Indented twice | >> | >This is indented copy >>This is indented even more |
Indented additional times | >>> etc. | >This is indented copy >>This is indented even more >>>This is indented even more |
You can add ordered (numbered) lists, unordered (bulleted) lists, and nested lists. Follow the instructions and examples below.
For this style... | Use these characters... | Like this... | |||||
---|---|---|---|---|---|---|---|
Unordered list (bullets) | + or - or * (followed by a space) |
|
|||||
Ordered list (numbers)* | Number plus period. For example: 1. (followed by period then space). |
|
|||||
Ordered list, not starting at 1 | Starting number in the first position (followed by period then space). |
|
|||||
Sub-list | List characters plus indent two spaces | - Java - Perl * sub first * sub second |
*On ordered lists, whatever number you use on the first item becomes the starting number. Whatever numbers you use for subsequent items, the list is numbered sequentially from the first number.
You can format whole lines or sections of code, or just a fragment of code that's an inline part of your content. See below.
For this style... | Use these characters... | Like this... |
---|---|---|
Inline | `{code text}` | Here is a code example inline: `var x = 10`. |
Code font plus box around | ``` {code text} ``` |
``` <licenses> <license name="Beta"/> </licenses> ``` |
To add a table to your markdown, use the hyphen and bar characters to create a grid. See below.
| Option | Description | | ------ | ----------- | | Discussion | Allows users to share information on a specific topic. | | Ticket | Reports an issue with a resource. | | Alert | Informs users about an issue. |
Alignment:
To right align table rows, use a colon at the bottom right of the header row as shown below.
| Option | Description | | ------:| -----------:|
To add a link, enclose the link text, that users will click, in a set of square brackets. Then put the actual URL in parentheses right next to it. See below.
[link text](http://www.example.com)
To add hover text to a link, add a forward slash after the URL, then add the hover text in double quotes, and then close the parentheses. See below.
[link text](http://www.example.com/ "title text!")
For example:
To find out more, go to [our website](http://www.example.com "find out more at our website!")!
Note: Depending on the platform settings, it's possible that markdown is enabled but links are disabled. If links are disabled and you add a link to an external site or resource in your markdown, you'll see an error message.
To add a horizontal rule, make a line of at least three of any one of the following characters:
___ ***
When you're adding a discussion, ticket, alert, review, or comment, and markdown is supported, you can upload an image file to display in your content. The supported image file types are:
When you're adding a discussion, ticket, alert, review, or comment, and markdown is supported, you can upload an image and display it inline in your content.
Follow the steps below.

When you're adding a discussion, ticket, alert, review, or comment, and markdown is supported, you can upload a file and then link to it inline in your content. Some examples of supported image file types are:
When you're adding a discussion, ticket, alert, review, or comment, and markdown is supported, you can upload a file and then link to it inline in your content. For example:
Download our tutorial PDF: [oauth_tutorial.pdf](oauth_tutorial.pdf "OAuth Tutorial PDF")
Follow the instructions below.
@[filelink](business-export.zip)