Install & configure

Install the Portal SuiteApp, enable the prerequisite NetSuite features, register the account with FullClarity's cloud infrastructure, and create one Portal Configuration record per subsidiary.

Module requirements

Portal needs the following NetSuite features enabled. Go to Setup → Company → Enable Features to turn them on:

SuiteCloud tab

• SuiteBuilder
  • Custom Records
  • Advanced PDF / HTML Templates
• SuiteScript
  • Client SuiteScript
  • Server SuiteScript
• SuiteFlow
  • SuiteFlow
• SuiteGL
  • Custom GL Lines
  • Custom Transactions
  • Custom Segments
• Manage Authentication
  • Token-Based Authentication

SuiteApp dependencies

Portal depends on Code Library, which installs automatically as part of any FullClarity SuiteApp install. No other FullClarity SuiteApps need to be installed first.

Installing the SuiteApp

Install Portal via the SuiteApp Control Centre. The deployment process installs all files and objects contained in the SuiteApp.

After install, register the account with FullClarity's cloud infrastructure (see below) before installing any other FullClarity SuiteApps — they will not function until Portal is registered.

Permissions

For administrators

To register the account with FullClarity, you need either the Administrator role or the FC Portal Admin role assigned to your user account.

For end users

Portal is infrastructure — end users do not interact with Portal screens directly. No additional permissions need to be set for the SuiteApp to function.

Register the account

Each NetSuite account needs to register once with the FullClarity Portal. The registration step is short but must be done by a NetSuite administrator. See Register a NetSuite account.

Create a configuration record

After registration completes, create a Portal Configuration record. In a single-subsidiary account create one; in OneWorld accounts create one per subsidiary that will store files or use Portal-backed integrations.

To create a configuration record:

1. Go to Setup → FullClarity Portal → Portal Configuration → New.
2. Choose the Subsidiary the configuration applies to.
3. Choose the API URL — usually https://my.fullclarity.com/api, which is preselected.
4. Choose the Storage Region — the AWS region your files will live in (USA is the default).
5. Save.

Repeat for every subsidiary that needs Portal-backed functionality. You'll need to run this each time you create a new subsidiary.

What success looks like

• The Portal registration confirmation email arrives shortly after running the registration flow.
• Opening Setup → FullClarity Portal → Portal Configuration shows one record per subsidiary.
• Installing File Storage, Certified Documents, or any Portal-dependent SuiteApp succeeds and their cloud-backed features work immediately.

Gotchas

• Sandbox refreshes wipe credentials. Re-register each sandbox after every refresh. Until you do, file upload, vendor portal, and other Portal-backed features will fail in that sandbox.
• Subsidiary mismatch. The Configuration record's chosen API URL and Storage Region apply to that subsidiary. If you create a new subsidiary in OneWorld, create a matching Configuration record before files are uploaded against the new subsidiary.
• Credentials from one account won't work in another. Each NetSuite account (production, sandbox) needs to be registered separately. You can't copy credentials between accounts.

Related

• Register a NetSuite account
• Refresh API credentials