Hubz.

TikTok / user.info.basic connection demonstration

TikTok Sandbox account connection

Establish a basic connection with the registered authorized Sandbox test account, while recognizing that publishing and profile-data access remain disabled.

PRODUCT VIEW

See how it works.

This TikTok Sandbox connection is a limited demonstration for a registered, authorized test account. The user reviews the provider-returned candidate and current account status. Basic permission is limited to user.info.basic; Hubz does not claim to store profile names, avatars, posts, analytics or a public provider identity through this workflow. A local account key and protected authorization information form part of the connection lifecycle. Video publishing is not included in this permission and requires a separate private Sandbox workflow.

Hubz.Workspace / Basic TikTok connectionDK
EXPLORE THE PRODUCT

Basic TikTok connection

Sample view
◎Limited basic scopeAccount and permissionsDepends on setup
↗Candidate connection approvalAccount and permissionsDepends on setup
⊙Visible statusAccount and permissionsDepends on setup
◇Lifecycle operationsAccount and permissionsDepends on setup
⌁Clear separation from publishingAccount and permissionsDepends on setup
01Verify Sandbox eligibility.
02Review the basic candidate.
03Track permission status.
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

Assuming a basic provider permission unlocks all profile data or content capabilities misrepresents data scope. A test target account must not be treated as operating under the same conditions as a general customer production account.

WHAT YOU CAN WORK TOWARDS

See which Sandbox target and basic permission are used for the connection. Manage its permission lifecycle without treating the connection alone as a publishing, analytics or content-reading service.

STEP BY STEP

How to use it.

  1. 01

    Verify Sandbox eligibility.

    Check that the target account is registered in TikTok developer configuration and the workspace is eligible for the pilot.

  2. 02

    Review the basic candidate.

    Approve the returned candidate and permitted actions for the connection demonstration, noting that publishing access is not enabled.

  3. 03

    Track permission status.

    Assess connection, reauthorization, removal and any required provider-side cleanup through the existing workflow.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Basic TikTok connection
Scope●Permission○Review○
Verify Sandbox eligibility.

Limited basic scope

Treat user.info.basic separately from content-reading or analytics permission.

FOCUS 02▤
Basic TikTok connection
Scope○Permission●Review○
Review the basic candidate.

Candidate connection approval

Complete the local connection decision for the authorized Sandbox target through user review.

FOCUS 03↗
Basic TikTok connection
Scope○Permission○Review●
Track permission status.

Visible status

Use screen state to determine whether a connection exists, needs reauthorization or has been removed.

FOCUS 04◇
Basic TikTok connection
Scope●Permission○Review○
Verify Sandbox eligibility.

Lifecycle operations

Assess local removal and provider-side permission-revocation steps against the relevant records.

FOCUS 05⌁
Basic TikTok connection
Scope○Permission●Review○
Review the basic candidate.

Clear separation from publishing

Make the team aware from the outset that video permission and final review are separate from the basic connection.

IN EVERYDAY WORK

What it looks like in practice.

Authorized Sandbox application administrator

Reviewing basic connection and removal for the registered target account.

Connection scope is assessed without assuming a video was published or profile/analytics data collected.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

This is a limited TikTok Sandbox basic-connection pilot. It is not offered as a generally available customer service without verification of application identity, registered target account, workspace, lifecycle and network eligibility.

  • The basic connection does not grant publishing, scheduling, content-reading or analytics permission.
  • This workflow does not store profile names, avatars, posts, analytics or a public provider identity.
  • The same ready-made scope is not promised for general production accounts outside the registered Sandbox target.
Compare plans

YOUR QUESTIONS

About this feature.

01Does the basic TikTok connection read my profile or videos?

The current basic scope does not provide those capabilities. The connection demonstration uses user.info.basic and a limited local permission record.

02Can I send a video after connecting?

No. Separate video.publish permission and a private Sandbox video review are required; the basic connection alone is not publishing permission.

RELATED WORKFLOW GUIDES

You may also need these features.

Social content preparationTrack the content lifecycle with brand-linked drafts, media, account targets and review steps.Brand libraryKeep brand name, website, logo, colors, connected accounts and graphic rules in a shared content-team record.Social publishing calendarReview plans using brand, account, provider, campaign and status filters, and preview eligible date changes.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Social Studio

Organize brand rules, content preparation, review, calendars and connected social accounts in a shared workspace.

02

Integrations

Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.

03

Security and team access

Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.