Apps in Microsoft Teams Pro Plus and Enterprise

Pin an app to a channel or group chat as a tab, and decide write requests from cards in Teams. Both use the same sign-in, roles and rules as the web app. Both need the Renly app for Microsoft 365 in your tenant and a plan with the Microsoft 365 integration: Pro Plus or Enterprise.

The channel tab

1. In a team channel or group chat, add a tab and choose Renly.
2. Sign in with your Microsoft account if asked (the same single sign-on as the personal tab). If you belong to several Renly organisations, pick one.
3. Choose an app, then one of its interfaces; the app's home interface is preselected. Save stays off until you have chosen.

The tab shows the app without Renly's chrome: the app's name, the interface's pages as tabs, and Open in Renly. Rows open their record pages inside the tab. Approvals (View request), automations, Requests, Data and Design open Renly in the browser. The tab follows the Teams theme live: light, dark and high contrast.

• The tab belongs to the organisation that set it up. A viewer who is a member of that organisation is switched to it; anyone else sees This tab is from another organisation.
• A viewer without access to the app, or whose role is not in the interface's audience, sees a plain message instead of the app.
• The tab cannot show Renly's terms dialog. Someone who has not yet accepted the current terms sees Before you can use Renly apps in Teams, accept the terms in Renly, with Open Renly and I've accepted, try again.
• On a plan without the Microsoft 365 integration, the tab shows the upgrade message instead of the app. The Apps entitlement (Pro Plus and Enterprise) still applies to every app call.

Approvals in Teams

When a write rule holds a change, each approver with a Teams identity linked in that organisation gets an Adaptive Card in their one-to-one chat with Renly, as long as the Renly bot is set up for the tenant and their Teams approval notifications are on (Settings > Teams).

• The card shows the app, the record, the field changes (choice labels and owner names resolved; at most ten, then a count), the rule and its message, who asked (an agent is named with the person it works for), how many approvals are needed, when the request expires in your time zone, and Approve, Reject and Open in Renly. Fields your role masks stay masked on the card; your rights decide which buttons you get.
• A click is decided as the Renly user your Teams identity is linked to, and the audit trail records that it came from Teams. Two-person rules hold: after the first approval the card loses Approve for that person, and a second click by the same person, or a click by the requester, gets the refusal as a message.
• A paused app, or paused agents for an agent's or automation's change, leaves the request open; the card says why and offers Reject only. A stale record fails the request and the card says so. An expired request, or one decided a moment ago elsewhere, shows its outcome.
• The card refreshes when you view it, so a decision made in Renly, by email or by another approver shows in Teams. Cards work in one-to-one chats only.
• The requester gets a card without buttons when their change is approved and made, rejected (with the reason) or failed.

Setting up Renly in Teams, including linking your Teams identity, is described under Agents and Automations and in the Teams settings page inside Renly.