> ## Documentation Index > Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt > Use this file to discover all available pages before exploring further. # The partner portal, for partners > What a fintech partner sees in the Marketing section of their sponsor bank's portal: submitting an asset, the quick check, what happens after you submit, the approval code, messages, and live pages with open issues. For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL. > [!NOTE] > > This guide is part of the [User Guides](https://docs.coverbase.com/user-guides/overview.md) collection. Share it with your partners. For the rest of the portal, see [The supplier portal, for suppliers](https://docs.coverbase.com/user-guides/supplier-portal-for-suppliers.md). For the bank's side, see the [Marketing compliance guide](https://docs.coverbase.com/user-guides/marketing-compliance.md). Your sponsor bank must approve marketing about the products it sponsors before it goes live. **Marketing** in your bank's portal is where you submit it, see where each review stands, get the approval code, and see which of your live pages the bank has a question about. The mistake people make most often is submitting the finished page after it is live. Submit the staging link early. The bank's approval is tied to the version it captured, and a page that is live before approval shows up on the bank's side as never approved. ## Getting in You sign in to your bank's portal the way you do for everything else: from a link in an email the bank sent, or by entering your work email at the portal's address and following the sign-in link. See [Getting in](https://docs.coverbase.com/user-guides/supplier-portal-for-suppliers.md#getting-in). **Marketing** appears in the portal's navigation when your bank has switched it on. If you do not see it, ask your contact at the bank. ## What is on the page **Marketing reviews** opens with four tiles and two lists. | Tile | What it shows | | - | - | | **In review** | Submissions waiting on the bank, and when the next decision is expected | | **Changes requested** | Submissions sent back to you, and the reply-by date | | **Approved, valid** | Approvals that have not expired, and when the oldest one does | | **Live issues** | Live pages the bank has an open issue on, and how many were never submitted | **Submissions** lists everything you have sent, with **Open** and **All** to switch between what is still in progress and the full history. Each row shows the **Asset**, its **Channel**, when it was **Submitted**, its **Status**, what is **Next** (a decision expected by a date, items to fix with a reply-by date, or **Valid until** a date) and the **Approval** code once there is one. | Status | Meaning | | - | - | | **Submitted** | Received, not yet picked up | | **In review with {bank}** | A reviewer has it | | **Changes requested** | The bank sent items back. Fix them and send a new version. | | **Approved** | Approved, with a code | | **Approved with conditions** | Approved, with conditions you must meet before it goes live | | **Rejected** | Not approved | | **Withdrawn** | You sent a newer version, which replaced this one | **Live assets with open issues** lists pages of yours the bank is watching that have something to fix, each with a short summary. A page marked **Never submitted** is live but was never sent for review: submit it, or tell the bank it is coming down. ## Submitting an asset Click **New submission**. ![The portal's Submit an asset for review page with a New submission card holding a Program picker, a Channel picker, a What is it field with the placeholder Savings landing page with the November rate change, an Asset field with a URL prefix and an Or paste the copy area, a Planned launch date, an Audience choice of Prospects US, Existing customers or Both, a Claims this asset makes checklist with A rate or APY, Fees or free, FDIC insurance, Speed such as instant, Bonus or reward, Security or safety, A comparison and Testimonial or creator, a Quick check before you submit card with Run quick check and two results each quoting a passage with a suggested fix, a line reading the bank's SLA for a website asset is 3 business days, and Save draft and Submit for review buttons.](https://mintcdn.com/coverbase/ASfsL9ARZRU6mOkd/images/user-guides/marketing-compliance-portal-submit.png?fit=max\&auto=format\&n=ASfsL9ARZRU6mOkd\&q=85\&s=68fe7e71770ce19b762d0fdd41f66b25) Submitting an asset: the program and channel, the link or pasted copy, the launch date, the audience, the claims the asset makes, and the quick check that runs before you submit. | Field | What to enter | | - | - | | **Program** | The product this asset markets. | | **Channel** | Where it will appear. The bank's SLA for that channel is shown beneath the form. | | **What is it** | A short title, such as the page and the change it carries. | | **Asset** | The **URL**, a file, or **Or paste the copy** for an email, post, script or ad. For a page, submit the staging link: the bank captures it, and the approval is tied to what was captured. Drop a file or **Choose file** for a PDF, an image (PNG, JPEG or WebP) or an email saved as .eml, up to 50 MB. The file uploads as soon as you choose it, and the review runs on the text read from it: a PDF's pages, the email's body, or the words visible in the image. | | **Planned launch** | When you intend to publish. | | **Audience** | **Prospects, US**, **Existing customers** or **Both**. | | **Claims this asset makes** | Tick what the copy says: **A rate or APY**, **Fees or "free"**, **FDIC insurance**, **Speed, such as "instant"**, **Bonus or reward**, **Security or safety**, **A comparison**, **Testimonial or creator**. Each one adds the rules the bank will check. | **Save draft** keeps the form on this device so you can come back to it. **Submit for review** sends it. The page then reads **Submitted to {bank}**. ### The quick check Once a link or pasted copy is in the form, **Quick check before you submit** runs the same checks the bank runs. Click **Run quick check** to run it again after an edit. For a file, the card reads **The check runs after upload**: the bank's checks run on the file's text once it is submitted. * **Nothing to fix. Every rule the check can test passes.** means the checks the form can run found nothing. The bank's reviewer may still raise something, and some rules need the bank's full review. * Each result quotes the passage, names the rule and gives a suggested fix. Fixing these before you submit usually saves a round. * **That page could not be fetched.** means the link did not load. Check it, or paste the copy instead. ### The rules before you submit **Before you submit**, on the Marketing reviews page, lists the rules the bank checks every asset of yours against, with the bank's sample language where there is some. **All N rules** expands the full list. Submissions that already meet them are usually approved in a day. ## What happens next Every submission goes through four steps, shown as **What happens next** on the asset. 1. **Captured.** The bank takes a copy of the page and ties the approval to it. 2. **Checked.** The bank's rules run. You see the result on the asset within minutes. 3. **Reviewed.** A reviewer decides within the bank's SLA in business days, and may ask questions in **Messages**. 4. **Approved.** You get an approval code to keep with the asset. Any change needs a new version. Open an asset from **Submissions** to see where it is. The bank sees only the asset version it captured, so if you change the page after submitting, submit it again. ### When the bank asks for changes The asset shows **Items to fix**: each item quotes the passage, names the rule and gives a **Suggested fix**, and **Note from {bank}** carries the reviewer's note. Fix them, then under **Send a new version** paste the corrected link or copy and click **Submit new version**. The bank reviews the new version against the same rules. **Versions** lists every version you have sent. ### When it is approved The asset shows the **Approval code**, such as `MKT-2026-0418`, and **Valid until** a date one year from the decision. **Download approval** gives you a file naming the asset, the program, the bank, the version that was approved, the date it is valid until and any **Conditions**. Keep the code with the asset in your own records; the bank's examiner can ask for it by number. An approval covers the captured version only. If you change the page, submit it again. Once the approval expires, submit it again too. ## Messages Each asset has a **Messages** thread with the bank's reviewer. Use it to ask about an item, say when a fix will ship, or tell the bank a page is coming down. The bank uses it to ask questions during review and to tell you when it has confirmed an issue on a live page. A message from the bank reaches your portal members by email. ## Live issues The bank watches your websites and app listings every day and compares what is live with what it approved. When the bank confirms an issue on a live page, the page appears under **Live assets with open issues** with the rule and the suggested fix, and the bank posts to the asset's thread. Fix the page; the bank's next sweep sees the change. You see only issues the bank has confirmed. An automated check the bank has not yet looked at is not shown to you. ## When something looks wrong * **Marketing is missing from the portal**: the bank has not switched the section on. Ask your contact at the bank. * **The quick check reads "That page could not be fetched"**: the link needs a sign-in, is blocked, or is mistyped. Paste the copy instead. * **A submission reads Withdrawn**: you sent a newer version of the same asset, and the bank reviews that one. * **An approved page is listed under live issues**: you changed the page after approval, or the approval expired. Submit the current page as a new version. * **A page you never sent is listed as Never submitted**: the bank's sweep found it live. Submit it, or tell the bank in **Messages** that it is coming down. * **Your draft is gone**: drafts are saved on the device you wrote them on, not in the portal. Write it again, or submit from the device you used. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.